Website migration services.
Move hosts, platforms or domains without losing data or rankings.
Migrations go wrong in predictable ways: redirects are forgotten and rankings disappear, email breaks because DNS was changed without thinking about MX records, or the cutover happens before DNS has propagated and orders are taken on a server nobody is watching. Every one of these is avoidable with a plan and a rollback path. I have moved a number of sites onto new infrastructure this way, including live PHP applications with scheduled jobs.
What’s included
- Server and hosting migration with verification
- Platform migration with content and data mapping
- Domain changes with a complete redirect map
- HTTP to HTTPS with correct canonical handling
- DNS planning, including email and MX records
- Cutover planned to minimise disruption
- Post-migration verification and monitoring
Redirects are where rankings are lost
If URLs change, every old URL needs a 301 to its closest equivalent. Miss them and you lose the accumulated authority of those pages, often permanently. This is tedious work and it is exactly the part that gets skipped when a migration is rushed.
Do not forget email
Changing nameservers without carrying MX and mail authentication records across is one of the most common ways a migration takes down a business's email. I plan DNS as a whole rather than treating it as just an A record change.
Verify before and after
Before cutover, the new environment is tested properly — not just the homepage. After cutover, I verify that redirects resolve, forms submit, email flows, scheduled jobs run and TLS is valid. The old environment stays available until we are confident.
Common questions
Will the site go down?
Downtime should be minimal to none. The new environment is prepared and tested in advance, and cutover is a DNS change with the old environment still running behind it.
Will we lose search rankings?
Not with proper redirects and preserved URL structure. Where URLs must change, a complete redirect map protects the transition.
Can you migrate email too?
Yes, including mailbox migration and setting up SPF, DKIM and DMARC correctly on the new host so mail keeps being delivered.
What about scheduled jobs and integrations?
These are part of the plan. Cron jobs, webhooks and API integrations all need to be verified on the new environment — they are a common source of quiet post-migration failure.
Have a project in mind?
Tell me what you're building and roughly when you need it. I reply to every genuine enquiry within one working day.