Assisted migration
A tested website migration, not a leap of faith
We move websites (WordPress included), mailboxes and DNS with a documented process: we clone the environment, test it against an agreed checklist and keep a rollback plan ready. The switch happens only when the tests pass.
How we migrate a website, step by step
There is no need to move everything on day one: we start with one or two sites and extend the scope once the checks pass.
What we do not promise
Assessment and inventory
We analyse the current environment: sites, DNS, mailboxes, certificates and technical requirements. Everything is collected in a shared inventory that remains yours after the work is done.
Plan and staging clone
We clone the environment onto a staging platform, cPanel-to-cPanel moves included, and define the verification checklist with you: critical pages, forms, mail, integrations and expected performance.
Acceptance test against the checklist
We run the checklist tests and document the outcomes. If something fails, we fix it and test again: we do not proceed with failed tests.
Agreed cutover, with a rollback plan
The DNS switch happens in a window agreed with you. The rollback plan stays ready: if a post-switch check fails, we return to the source environment and reschedule.
Final verification and dossier handover
We check site, mail and certificates after propagation, then deliver the updated environment dossier: access, configurations and what was done.
Honest, verifiable commitments
We do not promise zero downtime or absolute security: we promise a process that reduces risk and keeps every step documented and reversible.
Acceptance test with a checklist
The checklist is agreed before the switch and test outcomes are documented: you know what was verified and with what result.
Rollback plan
Until the post-switch acceptance is closed, the source environment remains available to fall back to: the migration is designed to be reversible.
Data export
Your data remains exportable in the formats set out in the contract, during and after the migration: portability is a commitment, not an obstacle.
Restore demonstrated on a sample
Before the cutover we demonstrate a backup restore on a sample of the environment: an untested backup gives no certainty.
What we need from you
An orderly migration is a two-party job: these are the things we ask of the client, declared before we start.
- Access to the current environment: hosting panel, domain registrar, DNS and mail management.
- A contact who can decide: sign-off on the checklist, the cutover window and the test outcomes.
- The list of connected services: mailboxes, integrations, APIs and automations that depend on the site or domain.
- Availability for the agreed tests: some checks (forms, payments, restricted areas) need your eyes.
- A realistic cutover window: we agree it based on your traffic and business activities.
Start with an assessment, not a removal van
Tell us what your environment looks like: we explain what the migration involves, what is needed and in which order it makes sense to proceed.