Migrate a section from Classic UI to Freedom UI

Level: beginner

The Creatio AI app development toolkit lets no-code developers migrate Classic UI sections to Freedom UI without manually rebuilding their list pages, form pages, expanded lists, and mini pages. The toolkit runs on the classic-to-freedom-migration skill: a coding agent rebuilds each section as a parallel Freedom UI counterpart based on the original section's structure.

The migration goes through multiple stages:

1. Analysis. The agent reads the Classic UI section from the environment. It reconstructs the structure: fields, expanded lists, and related pages.
2. Plan. The agent produces the migration plan as a single document.
3. Approval. Construction starts only after you approve the plan.
4. Construction. The agent builds the Freedom UI pages according to the approved plan and the interface design requirements. It builds child pages first, then the main page.
5. Verification. The agent reconciles the built result against the plan and produces the verification summary table.

These stages are governed by the following principles that shape how the agent works throughout the process:

• Parallel migration. The Classic UI section stays available. Creatio disables it only with your separate approval.
• Approval before construction. The agent produces a plan first and creates no Freedom UI artifact until you approve that plan. This is a mandatory step for any migration scope.
• Role split. A script handles the mechanical work: schema analysis and page construction. It produces a mapping table, and the agent adds its own analysis on top. You decide on scope and any ambiguous points.

Prerequisites

• A coding agent with the Creatio AI app development toolkit and clio MCP connected. Confirm the required setup with the agent.
• Access to the Creatio environment that contains the Classic UI section.
• A migration target: a link to the section, its name, or the name of a package or app.

Custom Classic UI logic is harder to analyze and reproduce. For this case, use Claude Opus 4.8 at medium effort, or GPT 5.5 (Codex) at medium effort.

Migrate the section

Follow these steps to migrate the section to Freedom UI.

Important

Approve the plan before construction begins. The agent creates no Freedom UI artifact until you approve.

1. Open your coding agent that has the Creatio AI app development toolkit and clio MCP connected.

2. Send the agent a request that states the target and asks to migrate the section to Freedom UI.

   The target can be a link, a section name, or the name of a package or app. Add the environment name if the agent cannot determine it from the link. Example requests:

   • "Migrate the Candidates section from Classic UI to Freedom UI. Environment: <environment name>."
   • "Here is the section: <link>. Build the migration plan for Freedom UI and submit it for approval."
   • "Migrate the entire Recruiting application to Freedom UI."

   The agent retrieves the section metadata from the environment on its own. You do not need to prepare or copy schemas manually.

3. Confirm that the agent states which skill it uses for the migration.

4. Review the migration plan that the agent produces.

   The plan describes the full scope of work before construction. It includes the following parts:

   Part	Description
   Overview	What is migrated and where, and the chosen approach.
   Main scope	A new Freedom UI page or an update to an existing one.
   List	List page columns, quick filters, and section actions.
   Form layout	All fields, groups, and tabs of the form page.
   Logic	Business rules, actions, and business process launch.
   To confirm	Checks to perform in the environment before construction.
   Child pages	A separate layout for each related form.

   Check that the plan reflects all Classic UI section elements:

   • Fields, tabs, expanded lists, and list composition.
   • The list page includes columns and filters.
   • The child pages and the mini page are present.
   • Every item marked for confirmation has a specific answer rather than an assumption.

5. Approve the plan.

6. Wait for the agent to build the Freedom UI pages.

7. Verify the result against the verification summary table. The agent builds this table from the pages it actually created.

   The table uses three statuses: "done," "missing," and "needs confirmation." Make sure the agent completed all tasks and skipped nothing. For a large task, the agent may pause to clarify scope and next steps. For example, it may ask whether to review an intermediate result before continuing.

As a result, the section exists as a parallel Freedom UI counterpart: its list page, form page, expanded list, and mini page. The original Classic UI section stays unchanged. Confirm completeness in the verification summary table: every element shows the "done" status, with no "missing" or unresolved "needs confirmation" items.

Watch for deviations from the process

Clarify the agent's progress if you notice any of these signs:

• At the start, the agent did not state that it would use the migration skill.
• The agent shows only part of the migration plan and links to the detailed plan — the "plan.md" file — instead.
• Construction started before you approved the plan.
• The agent provides a shortened "done" table instead of the detailed verification summary table.
• The agent simplified the plan without approval — for example, merged groups or simplified a component.
• The agent postponed items that need confirmation instead of verifying them in the environment.

If any of these happen, point the agent to the discrepancy so it can correct the error.

Functionality available for migration

The migration covers functionality that standard Freedom UI components support.

Section list page:

• Layout
• Custom filters
• Business process launch
• Report print button
• Custom section actions
• Custom buttons

Form page:

• Page layout and standard content (inputs, field groups, expanded lists)
• Page business rules
• Simple page customizations
• Business process launch
• Report print button
• Custom record actions
• Expanded lists with their pages

note

You can now simplify the transition from Classic UI to Freedom UI by migrating dashboards using a dedicated Dashboards migrator Marketplace application. The app provides a manual migration mechanism via a Migrate button and supports dashboards from the Dashboards section as well as dashboards embedded in other sections, such as Accounts and Contacts. Learn more: Dashboards migrator (Creatio Marketplace).

---

See also

Creatio AI app development toolkit

Set up Creatio AI app development toolkit

Start working with Creatio AI app development toolkit