Start with an outcome and a source
A project brings the intended outcome, business area, delivery lead, destination, environment and target date together. Create the project before importing, or connect the project discovered from an export to its delivery plan.
The source identity matters. A project-specific import uses the selected project as its destination, while existing owners, plans and evidence remain attached to that project. Use the Catalog to inspect jobs, sequences and dependencies before deciding what to move.
Turn scope into migration groups
Choose related jobs and a target platform to create a migration group. Inspect prerequisites, sequence relationships and scope findings before committing to the selection. Schedule groups in project waves with dates and milestones so delivery has a structure beyond a list of jobs.
A shared source job keeps one delivery record per destination even when several migration groups include it. The owning migration coordinates that work; the other groups retain their connection to its progress and evidence.
Make responsibility explicit
Assign delivery roles and agree acceptance criteria before generating and reviewing code. Engineers, test owners and reviewers can follow their next actions through My work, then open the migration record with its current revision and outstanding findings.
Project planning and account access serve different purposes. A delivery assignment says who owns the work. Administrators manage which accounts can access it and which actions their roles permit.
Set team access around the project
Administrators can choose estate-wide or assigned-project visibility, grant project access, and control access to Catalog, Migrations, Releases, Reports and AI Migration Assistant. Team policy also supports assigned approval and independent review requirements.
Client accounts and project permissions separate customer workspaces in the shared application. Dedicated deployments can use customer-specific data directories and identity configuration.
Keep decisions connected through handover
Follow source scope, generated code revisions, review decisions, test evidence and acceptance from the project. Changed source or code can make earlier evidence stale, bringing the work back for review.
After acceptance, record the production destination, release evidence, cutover verification, rollback procedure and operations handover. The overview distinguishes accepted migration work from completed operational handover.