Migration stages and what to expect

Every migration request has a progress timeline on its page under Migrations. Each stage tells you who is working on it and whether anything is needed from you.

The stages

1. Submitted: we have received your request.
2. Under review: our team is assessing your source environment and the scope.
3. Plan recommended: for moves to YallowHost, we suggest the destination service that fits your workload.
4. Quote sent: the price for paid work is ready for you to review.
5. Approved: the plan and any quote are agreed, and work is scheduled.
6. In progress: data is being copied and configured.
7. Waiting for customer: we need something from you, such as corrected access details, a decision or a DNS change.
8. Completed: the migration is finished.

A request can also be Cancelled if it no longer applies.

Quotes and ordering the destination

An estimate shown on the form is a starting point. The confirmed quote reflects the actual data size and the optional services you chose. For moves to YallowHost, you order the recommended hosting plan or cloud server as normal, so the destination is ready before data is copied.

When we are waiting for you

If a request shows Waiting for customer, check the latest note on the request and your email. The most common reasons are credentials that do not work, a missing detail about the source, or the need to update DNS. Replying promptly keeps your migration moving.

The cutover

Once data is in place and checked on the new service, the final step is pointing your domain at it by updating nameservers or DNS records. We tell you exactly what to change, or make the change for you when DNS migration is part of the scope. Allow time for propagation; see DNS propagation and troubleshooting.

After completion: verify everything

• Browse key pages and test forms, sign-in, search and checkout.
• Send and receive email from each mailbox.
• Confirm scheduled tasks, payment callbacks and integrations work from the new server.
• Check that your website loads over HTTPS without certificate warnings.

Keep your old service running for a few days after cutover in case anything was missed, then cancel it. Change any passwords you shared for the migration, and remove temporary accounts you created for it.