Service Migration Centre

Migration with preparation and verification

A service migration is not only a file copy. Website files, databases, email, DNS, SSL, domains, server settings, licences and scheduled tasks can all affect the result. Nettescil approaches migration as a sequence of preparation, transfer, validation and controlled cutover.

Before the move

Inventory domains, applications, databases, mailboxes, DNS records, certificates, versions, cron jobs, integrations and access responsibilities. Confirm the source archive can be opened and the target has enough resources.

Files and databases

Use a documented archive and record the database version, character set, collation, users and scheduled tasks. Restore into a controlled area first, then check files, media, uploads and important records.

Email and DNS

Email requires separate attention because MX, SPF, DKIM, DMARC, mailbox access and queues are different from website traffic. DNS changes should wait until the target site and mail path are tested.

SSL and acceptance tests

Check certificates, HTTPS redirects, login, forms, uploads, database actions, payment steps, API connections, cron and customer panel. A 200 response alone is not an acceptance test.

Rollback and aftercare

Define the rollback record, TTL expectations, monitoring window and support owner. After cutover, compare public routes, mail delivery, logs and customer-visible results.

Share a migration request through the Nettescil contact page.

Frequently asked questions

Can every migration be completed instantly?

No. Scope, data, email and DNS determine the timing and risk.

Should DNS change first?

Normally the target should be prepared and tested before traffic is changed.

Are backups enough?

Only when integrity and recovery have been checked.

What should I provide?

Source and target details, domain list, application, backup, email scope and target date.