We advertise free migration assistance for Web Hosting and NabWP. The first step is to tell us what you want to move so we can check the source environment, destination package and access needed. A WordPress website moving into NabWP and a general hosting account containing several applications and mailboxes require different migration plans.
IN THIS ARTICLE
01 Prepare the details our migration team needs
- Provide the website addresses, the current hosting or control-panel type, the application involved and an approximate size.
- Explain whether the site receives orders, bookings, uploads or other changes during the day.
- Also list email accounts and any external services connected through DNS.
Those details help us identify what must be copied and what should remain with another provider.
02 Keep access available and agree the migration scope
Do not cancel the old hosting before the migration has been checked. We may need continued access to copy data, compare the result or collect changes made during the move. Use the secure access method agreed with our team for any credentials. Ordinary public chat is not the place to paste hosting passwords, private keys or customer database exports.
The goal is a carefully planned move with disruption kept as low as practical. It is not possible to promise identical timing or zero downtime for every source host and application. Access restrictions, incompatible software, large databases and changing live data can affect the work. Domain registration and email migration should also be discussed explicitly instead of assumed to be part of every website transfer.
03 Test before sending visitors to the new hosting
Once the destination is ready, test its important pages, login, forms and application functions before changing live routing. For a store, review the final order-data handling with us. Keep the original service available until you have confirmed the new site and any included mail services are working as intended.
04 Example: prepare a complete migration request
Copy this outline into your migration request and replace the bracketed fields. It helps the team agree the scope before arranging secure access.
Website addresses: [domains to move]
Source host and control panel: [provider and panel]
Destination Nabtech service: [service reference]
Approximate files and database size: [sizes]
Mailboxes: [move these accounts, or keep email with current provider]
Live changes: [orders, bookings, uploads or form submissions]
Scheduled tasks and integrations: [what must keep running]
Essential tests: [login, contact form, checkout or other functions]
Preferred handover window and timezone: [availability]Leave passwords, private keys and database exports out of this outline. Agree the transfer method separately. State explicitly when the domain registration or an external email service should remain with its current provider.
What should be agreed before a free migration begins?
- List every website, mailbox, database, scheduled task and externally hosted service associated with the source account.
- Agree what is included in the move, how access will be supplied securely and when any final changing data will be copied.
- Prepare a test checklist and keep the source available until the destination and the agreed email services have been verified.
A website transfer does not automatically transfer the domain registration, an external email subscription or a software licence. Identify who controls each dependency. For a store, agree how recent orders and payment notifications will be preserved during the final handover.