Migrations
What to collect before moving web hosts
A hosting move is much easier when the source material is collected before anything changes. You do not need to understand every server setting. You do need a complete copy, a short inventory, and continued access to the old account until the new copy is proven.
Start with the website address and hosting product
Write down the public website address and the exact hosting product shown on the bill or dashboard. A company may sell cPanel hosting, managed WordPress, a website builder and VPS service under the same brand. Those products do not use the same export process.
- Website address
- Hosting company
- Product or plan name
- Control panel name, if one is shown
Collect files and databases as a matched set
Most content management systems need both website files and a database. The files contain code, themes, plugins and uploaded media. The database contains pages, posts, users, settings and often store orders.
Create the two exports close together in time and label them with the same date. Keep the original copy on your computer until the move is complete.
Record DNS and email separately
The website host, DNS provider and email provider may be three different companies. Copy the current DNS records and list every mailbox, forwarder and mailing service before cutover. Moving a website must not silently move or break email.
Use temporary access instead of sharing a permanent password
If an automated route needs panel access, create a temporary restricted credential where the old provider supports one. Easy Migration asks for private access only after sign-in and only when the chosen transfer method needs it.
Do not disable multi-factor authentication just to make a migration easier. A backup upload or assisted route is safer when temporary access is unavailable.
Keep the old service until verification is complete
A copied site is not automatically a correct site. Test important pages, forms, logins, scheduled jobs and checkout flows on the destination. Take a final sync for changing data, approve cutover, and retain the old account through the rollback window.
Common questions
Do I need to change DNS before the migration?
No. Copy and test the site first. DNS changes belong near the end, after the destination is ready and you have approved the cutover plan.
What if I cannot find my current host?
Start with the website address. Public DNS and platform signals can often narrow the provider, but the account owner should still confirm the product before private access is requested.