Completed work
A domain migration with email continuity
The website was moving. The business still needed its email. Treat the domain change as several connected jobs, not one switch.
The problem behind the job
If a domain changes, the website is only one dependency. Email and other services need to keep working while the new domain takes over.
What I was working with
I handled a website-domain migration that involved mapping front-end and product URLs to a new site while preserving the existing email service during the transition. The work needed to distinguish where the website should send visitors from the services that still depended on the old setup.
Map the old pages to sensible destinations
The migration work covered the old website's front-end and product routes. The aim was to connect those URLs with the appropriate pages on the replacement site.
It was not simply a case of treating every old address as the same homepage visit.
Keep email continuity separate
The existing email service remained available while the website transition and redirects were handled. That was part of the practical scope, not a detail to discover after the site moved.
A domain can be involved in more than the website people see in a browser.
What was delivered
The source history records the migration and redirect work as delivered, including the email-continuity requirement.
This example does not claim zero disruption across every service or a guaranteed preservation of every search position.
What else depends on the domain you are moving?
If your problem looks similar, send me the current setup and the outcome you need. The implementation may be different, but the same kind of thinking usually applies.
What I'd establish before another move
The old URLs, the intended destination structure and the services using the domains should be listed first. Access, responsibilities and the checks after the change need to be agreed.
The migration checklist makes those dependencies easier to see.
A move with a defined scope
A migration can overlap with content recovery or catalogue rebuilding, but those are not automatically the same task. Migration and recovery explains the wider work.
For content that has already lost its images, see the image-repair example.
HAVE SOMETHING AWKWARD?
What else depends on the domain you are moving?
Send me the URL, what is happening, what you have already tried and what a useful result would look like. A small anonymised sample is enough to start - do not send passwords, credentials or sensitive customer data.