Test the destination copy before directing public traffic to it.
Applies to: Website and email migrations
A safe migration separates data transfer from DNS cutover. Copy and test first, lower risk at the change window, then keep the old service intact until website, email and background tasks have been verified.
Before you start
- Sign in to the Customer Portal and open the affected hosting service.
- Take a current backup before changing website files, databases, DNS or application configuration.
- Allow for DNS caching and avoid making unrelated DNS changes during the same maintenance window.
Step-by-step
- Use a temporary URL or local hosts-file override when provided.
- Test forms, logins, payments, scheduled tasks and email.
- Compare recent data with the source.
- Approve a final synchronisation window for dynamic sites.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| Some networks show the new result while others show the old one. | Recursive DNS caches have not expired or authoritative nameservers do not return consistent data. | Check the authoritative answer first, compare all listed nameservers and wait for the previous TTL before making another change. |
| The domain returns NXDOMAIN or SERVFAIL. | The zone is missing, delegation is wrong, DNSSEC is broken or an authoritative server is not responding. | Verify delegation at the registry, confirm the zone exists on every authoritative server and remove stale DS records only through a controlled DNSSEC rollback. |
| The restored site opens but behaves incorrectly. | Files and database were restored from different times, cached data is stale or configuration still points to the old location. | Align the restore points, clear application caches and verify URLs, credentials and scheduled tasks before declaring recovery complete. |
| Recent data is missing. | The selected recovery point predates the change or the data was stored outside the backed-up location. | Stop making further changes, identify the required timestamp and ask support what recovery points remain available. |
Important notes
- Make production changes in a planned window, keep the old configuration recorded and avoid changing several dependent services at the same time.
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The affected domain and SiteWorx account
- The exact error text and time
- The last change made
- Relevant log lines with passwords and personal data removed
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Moving from cPanel or another control panel
- Migrate hosted email
- Prepare a site for migration
- Request a website migration
Last reviewed: 2026-07-18.
