Define the checks before the build.
Choose representative user journeys, record counts, access rules and important URLs. These checks give the team a concrete way to compare the replacement with the service it must preserve.
The migration approach
Six phases. Clear decisions.
Start with a read-only inventory. Define what must work, rebuild the agreed features and check the result before moving production traffic.
From inventory to approved cutover.
- 01
Inventory
Map pages, routes, data, users, files, jobs and integrations. Establish what must keep working.
Read-only inventory - 02
Approve the plan
Review architecture, feature gaps, data handling, costs and acceptance checks before implementation.
Approval gate - 03
Build the application
Implement the agreed frontend changes and Motoko backend. Recreate the critical workflows and integrations.
Working application - 04
Move data & files
Where needed, import data and files in controlled batches. Check records, relationships and file integrity.
Checked data & files - 05
Rebuild sign-in
Where needed, implement sign-in and verified account linking. Test roles, permissions and administrator journeys.
Verified access - 06
Approve cutover
Review test results, recovery procedures, source code and operating instructions. Approve any write freeze, DNS change and decommissioning separately.
Approval gate
Start the inventory in your project.
The migration skill includes the workflow, platform notes and reference tools for your developer or AI coding agent.
Get the migration skill