What needs to move
Check moving from Azure by inventorying VM disks and services alongside virtual networks, managed identities, load balancers, databases, storage, DNS, application services, and secrets that may require redesign during migration.
Migrate from Azure
Review application runtimes, data, identity and network dependencies. Agree on replacements for Azure-specific services before migration.
Hosting options
Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →02Tell us what you need to host and when it needs to be ready.
See Ask about your project →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →Your requirements
Check moving from Azure by inventorying VM disks and services alongside virtual networks, managed identities, load balancers, databases, storage, DNS, application services, and secrets that may require redesign during migration.
Copy the site or application to the new host and test it privately. Check logins, forms, database writes, scheduled jobs, email and any external integrations.
Choose when to stop or synchronize new writes. Include orders, uploads and mail that arrived after the first copy. Avoid letting both systems accept independent changes.
Save the old DNS and routing settings. Switch traffic after the final tests, monitor the result and keep the old service until the agreed rollback period has passed.
Field guide
An Azure deployment organizes everything into resource groups, and the group view is the inventory. Inside it sit virtual machines and their managed disks, plus virtual networks, public addresses, load balancers, Azure SQL or MySQL databases, storage accounts and App Service sites. Export data from each resource type with its own tool, because a disk snapshot alone rebuilds nothing managed.
Managed identities hide the credentials. Applications on Azure often connect to databases and storage through an identity the platform supplies, so no password exists anywhere in the code to copy. Find every identity based connection during the inventory, create real credentials for the destination services, and test database, storage and mail connections with those credentials before traffic moves.
Export or screenshot the full resource group list. It is the only view that shows every service the deployment quietly depends on.
List the secrets and certificates the workload reads from Key Vault. Each one needs a destination home and a rotation decision.
Sites on App Service have no server to copy. Export the site files and its database directly, plus the app settings that hold connection strings.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.