Turn the answers into a plan.
Use your application’s inventory to identify the decisions that apply to your service, then agree the scope and checks with your team.
See the migration approachQuestions worth asking
Before you commit.
Understand the decisions behind a migration, from the first service you move to the systems and responsibilities you retain.
Practical questions about the move.
Can we start with one service?
Yes. Choose one clearly defined service, identify its dependencies and agree what must work before moving it. Establish which system owns each part of the data during the transition.
Do we have to move the frontend too?
No. Your frontend can stay on its current host and call the Motoko backend, or move to ICP too. Review required changes to API calls and sign-in. A retained host remains part of your security responsibilities.
What happens to our users and their logins?
Plan sign-in and verified account linking explicitly. Internet Identity and supported enterprise SSO are options, with provider and domain configuration where required. Roles and permissions must be rebuilt and tested; existing password hashes are not copied over. See the enterprise SSO guidance.
Can we keep our domain and our links?
Keeping the domain and important URLs is part of the migration plan. Map existing routes, redirects and .php links, then test them before approving DNS cutover.
Where does our data live?
ICP stores application code and data in units called canisters, replicated across a group of computers called a subnet. Review available locations and the complete architecture against your data requirements. Standard canister data should not be treated as confidential from node operators; review encryption and secret handling before moving sensitive data. Read the subnet selection and data storage guidance.
Can we choose who operates the infrastructure?
Open Cloud describes sovereign cloud engines built from nodes you select by operator, geography and hardware class. These engines remain part of the Internet Computer network. Operator choice is separate from application access and data confidentiality.
Open Cloud currently invites early-access applications. Confirm available operators, supported hosting models and your isolation requirements with its team before committing. See the provider program status.
What does it cost to run?
Costs depend on the deployment model. Standard ICP application canisters use credits called cycles; Open Cloud engines have separate infrastructure funding. Estimate the chosen setup and retained services with realistic traffic, then assign a funding and monitoring owner. Compare ICP cycle costs and Open Cloud pricing.
What if something goes wrong during the move?
Agree how to return to the previous service before switching production traffic. Test recovery and data checks, including how records created during the transition will be handled. A snapshot alone does not reconcile records changed in both systems.