Skip to content
UK web hosting, domain names, email, website security and online services.

Migrate customer sites into a reseller account Print

  • account, migration, reseller
  • 0

Plan migrations account by account to preserve isolation and simplify rollback.

Applies to: Reseller migrations, security and support

Migrations, security incidents and account termination can affect customer data. Use written change records, maintain independent backups and confirm authority before destructive actions.

Before you start

  • Sign in with the reseller account rather than a customer SiteWorx login.
  • Identify the affected SiteWorx account, package and domain.
  • Record the current package, DNS and account settings before making a production change.

Step-by-step

  1. Create the destination SiteWorx account.
  2. Copy files, databases, mail and scheduled tasks.
  3. Test using a temporary method.
  4. Coordinate DNS cutover and monitor after launch.

Common problems

SymptomLikely causeWhat to do
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.

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 reseller service and affected SiteWorx account
  • The package name and current resource use
  • The exact action attempted and error returned
  • Whether the issue affects one or multiple customer accounts
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

Last reviewed: 2026-07-18.


Was this answer helpful?

« Back