Reseller · Migration
Agency hosting migration without stopping client work
Moving ten, twenty or fifty client sites is not one heroic night of work: it is a process. We start with a test migration of one or two sites, verify everything against an agreed checklist, then move the rest on a calendar coordinated with your deadlines. Every step has a rollback plan and, at the end, we hand over a complete inventory of the environment.
A test migration first, then the portfolio
We do not ask you to move everything on day one. Together we pick one or two representative sites, by technology, traffic or criticality, and migrate them first with full acceptance testing. The test migration serves three purposes: proving the process on your real case, showing your stakeholders how we work, and measuring actual timings before planning the rest.
Only once the first sites pass the verification checklist do we plan the portfolio, in batches: each batch has its own agreed window and its own rollback plan. If a site fails the tests, it goes back to the source environment while we analyse why, without dragging the others down with it.
Throughout the migration the source environment stays live: the DNS switch happens only after acceptance testing passes, in a window you choose.
The site migration checklist: DNS, email, rollback
Every migrated site goes through the same checks, documented and shared with you before the cutover.
DNS and certificates
An audit of existing records, TTL reduction before the switch, and zone and TLS certificate checks on the new environment before and after the cutover.
Email is the first thing that breaks in badly run migrations: we verify mailboxes and MX, SPF, DKIM and DMARC records, and agree how mail is handled during the transition window.
Content and functionality
A copy of the site on staging, comparison with the original and agreed functional tests (forms, restricted areas, checkout where present) before the DNS switch.
Rollback plan
Defined for each batch before the cutover: what is checked, within what time, and how to return to the source environment if tests fail. Rollback is part of the plan, not an improvisation.
The migration process, step by step
The same process as the test migration repeats on every batch of the portfolio, with timings that by then are already measured.
Written commitments, not promises
Portfolio inventory
Together we list sites, domains, DNS, mailboxes, access and technologies. The inventory is shared from the start and underpins every later decision.
Test migration of one or two sites
We copy the first sites to staging, run the full checklist and agree the acceptance criteria with you. The cutover happens only once tests pass.
Coordinated calendar
We plan the following batches around YOUR deadlines: client launches, campaigns, seasonal closures. You choose the cutover windows, we respect them.
Batch migration with rollback
Each batch follows the same checklist as the test migration: staging, verification, cutover in an agreed window, rollback plan ready. Every operation performed is logged.
Final check and inventory handover
Once the portfolio is migrated we check sites, email and certificates, then hand over the updated environment dossier: domains, DNS, accounts, configurations and the operations log. The environment stays readable and yours.
Agency site migration FAQ
How long does a portfolio migration take?
It depends on the number and complexity of the sites: that is why the test migration measures real timings before planning the rest. The calendar is built around your deadlines, not ours.
Will my clients notice the move?
The process is designed to avoid exactly that: cutovers in agreed windows, email verified before and after, rollback plan ready. Communication with your clients remains yours, and we plan it together in the calendar.
What if a site does not work after the cutover?
The rollback plan defined before the switch applies: the site returns to the source environment while the problem is analysed. Rollback is part of every batch's checklist.
Who handles email during the transition?
Email handling in the transition window is agreed in the plan: MX records, mailboxes and propagation times are on the checklist, because that is where improvised migrations fail.
What do I receive at the end?
The environment dossier: an inventory of domains, DNS, accounts and configurations, plus the log of operations performed. It gives you control, and makes the exit path concrete if one day you want to leave.
Start with a portfolio assessment
Tell us what your portfolio looks like: we will propose the test migration, the checklist and a calendar built around your deadlines, with a written offer before any work starts.