Inventory
Every page, address, form, integration and scheduled job on the current site is listed, along with anything that has to be recreated rather than copied.
Content, media, addresses and search positions all come across. The move is planned first, verified twice, and switched over in a window you choose.
Nobody notices a good migration. The site looks the same, the addresses work, the forms still arrive and the rankings do not move. All the work is in the part that stays invisible: the inventory, the redirects, the DNS timing and the checks after the switch.
A bad one is obvious within a week. Images missing from old posts, forms going nowhere, Search Console filling up with 404s, and a slow slide down the results that nobody connects back to the move.
So we do it in the order that makes failure visible early: inventory first, a full copy running and verified before anything is pointed at it, and a redirect map checked line by line rather than assumed.
Content dumped into a file and pasted back in. Formatting breaks, media loses its links, and half the metadata never arrives.
Files moved, DNS switched the same evening, problems discovered by visitors over the following week.
Inventoried, copied in full, verified on the new host, then switched with redirects and monitoring already in place.
Whether it is a new host, a new platform or a new domain, the job is the same: everything arrives, nothing breaks, and you hear about problems from us rather than from a customer.
An inventory before anything moves
Every page, address, form, integration and scheduled job is listed first, so we know what has to exist on the other side.
A full copy, not a partial export
Database, uploads, themes and configuration move together. Content keeps its formatting and media keeps its links.
Checked before the switch, watched after it
The site is tested on its new home while the old one is still live, and errors, 404s and positions are monitored in the days that follow.
DNS, certificates and mail records handled
The cutover is planned ahead, SSL is issued before the switch, and mail records are checked so existing email keeps arriving.
Mailboxes moved between providers
From a custom mail server to Google Workspace, from Google Workspace to Microsoft 365, or the other way around. Mail, folders, contacts and calendars come across, including shared mailboxes, and the changeover is scheduled so nothing bounces.
A redirect map and Search Console
For a domain or structure change, every old address is matched to its replacement and Google is told about the move.
Platform
WordPress
Content
Moved as data
Addresses
301 map
Search
Console and sitemaps
Cutover
A window you choose
The new host is configured for the site that is arriving, not left on defaults.
Hosting
Configured, not default
PHP version, memory, caching and object cache set for the site rather than whatever the plan ships with.
Images
Arrive intact
Media comes across with its sizes in place, then is served compressed and in modern formats.
Caching
Set up at the new home
Page and asset caching configured after the move, not carried over from a stack that no longer applies.
Checks
Measured, not assumed
Load times compared before and after, so a move that made things slower gets caught immediately.
The current site keeps serving visitors until the last step. Nothing is switched until the new one has been checked.
Every page, address, form, integration and scheduled job on the current site is listed, along with anything that has to be recreated rather than copied.
Database, media, themes and configuration are copied to the new host and brought up on a temporary address.
Content counts, media, forms, checkout, logins and integrations are tested on the new copy while the old site is still live.
For a domain or structure change, every old address is matched to its replacement and checked before the switch.
DNS is switched in a window you choose. SSL, email and analytics are confirmed the same hour.
404s, errors and search positions are monitored, Search Console is updated, and the old host stays available until we are sure.
A hacked portal rebuilt on a dedicated server, with the forum moved and rankings kept.
Read the case study
A complete redesign and WooCommerce catalog for an industrial equipment distributor.
Read the case studyContent moves as data. Volume changes the timeline, not the method.
You are never caught between two broken sites. The switch is the last step, not the first.
Errors and positions are watched in the days that follow, and we can keep the site maintained from there.
Three situations, three prices. Which one you are in depends on where the site is going, not on how big it is.
Moving in to us
You are taking a care plan, and the move onto our servers is part of it.
Move to your own host
A straight move to a server you choose. That is the price for an ordinary site; a large one is quoted after we look.
Domain or structure change
Every address changes, so every address has to be mapped and then watched.
Mailbox moves are quoted separately, per account. Moving a website does not touch your email unless you ask us to move it.
The practical questions about downtime, rankings and what a move costs.
If we host and maintain the site, moving it in is free. A straight move to a server of your own starts at 50 EUR. A domain change, where every address has to be mapped, Search Console updated and positions watched afterwards, is quoted after we have seen the site. Mailbox moves are quoted separately, per account.
No. The copy is verified on the new host while the current site is still serving visitors. The switch itself takes minutes, in a window you choose.
On a host move the addresses do not change, so there is nothing to lose. On a domain or structure change every old address is mapped to its replacement, Google is told about the move, and positions are watched afterwards.
There is no practical ceiling. The largest single move so far was around 7,000 posts and 200,000 images. Size changes how long it takes, not whether it works.
Yes. Moving content into a different site or a different design is a common request and is handled the same way, as data.
Yes, though a platform change is a rebuild with a content migration attached rather than a straight copy. We tell you which one your case is after looking.
Yes. Mail records are checked before and after the switch, so messages keep arriving. Moving a website does not touch your mailboxes unless you ask us to move those too.
Yes, and that is its own job rather than part of a site move. A custom mail server to Google Workspace, Google Workspace to Microsoft 365, or the other way around. Mail, folders, contacts and calendars all come across, including shared mailboxes, and the changeover is scheduled so nothing bounces while it happens. It is quoted per account, once we know how many mailboxes there are and how much history.
No. We can move you to our servers or to a host you have chosen. If you want us to maintain the site afterwards it does need to sit where we can support it, and we say so upfront.
It stays available until we are certain the new one is right. Nothing is deleted on the day of the switch.