Ditch Microsoft & Google Today!
Moving a website or a company’s email is the job everyone puts off. It is also the one we do every week. Our migration team moves sites, databases, mailboxes, DNS and SSL from most hosts and platforms, and nothing at your old provider is touched until you have seen the new one working.
Free on most plans. We review what you have and tell you the scope before anything starts.
“A year ago, I decided to migrate my website to their hosting platform in order to move away from big tech, and gradually, moved all of my domains over. Customer service is 5 stars. You get a one-to-one relationship as well as fast, friendly and knowledgeable service.”
Donna Gentile · Google review
The pieces that have to move together for a switch to be invisible to your customers. Anything unusual in your stack is flagged in the review before we begin, rather than discovered halfway through.

What moves | Scope | Detail |
|---|---|---|
Website files and databases | Every site on the account | WordPress, WooCommerce, Joomla, Drupal, Magento, static sites and custom applications |
Email accounts and mail history | Mailboxes, folders, filters and contacts | IMAP transfer from most providers, including Google Workspace, Microsoft 365, Zoho and cPanel mail |
DNS records | The full zone, not just the A record | MX, SPF, DKIM, DMARC, CNAME, TXT and any service records your tools depend on |
SSL certificates | Reissued and installed | AutoSSL on arrival, or your existing paid certificate reinstalled |
Cron jobs and scheduled tasks | Rebuilt on the new server | The ones that silently break a migration if nobody checks them |
Redirects and rewrite rules | .htaccess and server configuration | So your search rankings and inbound links survive the move |
Your site runs on our server at a temporary address while your current host keeps serving real traffic. You click through it, check the forms, check the checkout, and only then do we touch DNS. If something is wrong, nothing has broken, because nothing has switched.
We look at what you are actually running first: how many sites, how large the databases are, how many mailboxes, and anything unusual in the stack. Migrations go wrong when somebody guesses, and we would rather find the surprise before it becomes your week.
Mail is the part that hurts when it goes wrong. We transfer mailboxes with their folder structure and history over IMAP, then cut the MX records over at a quiet time. Nobody loses a message and nobody spends a morning reconfiguring Outlook alone.
Redirects, rewrite rules and URL structure move with the site. A migration that drops your URL structure costs you search positions you spent years earning, and it is entirely avoidable.
After DNS switches we monitor the first two days: mail flow, SSL, error logs and form submissions. Most migration problems surface in that window, and we would rather catch them than have you report them.
Keep your old plan running until the new one is proven, then let it lapse. Anyone telling you to cancel before the move is making their job easier and your week worse.
The platforms we move sites and mail off most often, and what changes when you land. If your current platform is not listed, ask — the list below is the common cases, not the limit.
Moving from | How it goes | What to expect |
|---|---|---|
cPanel hosts | Straightforward | A full cPanel account backup restores cleanly on our side, including mail and databases |
GoDaddy, Bluehost, HostGator, InMotion, Hostinger | Straightforward | Standard shared hosting moves; we handle the panel differences |
WP Engine, Kinsta and managed WordPress hosts | Straightforward | Sites move with plugins, themes, uploads and database intact |
Wix and Squarespace | Rebuild required | These platforms have no export that recreates the site elsewhere. We quote a rebuild and tell you that up front |
Google Workspace and Microsoft 365 mail | Straightforward | Mailboxes, folders and history transfer over IMAP; calendars and contacts export separately |
Proton Mail, Fastmail, Zoho and other mail hosts | Straightforward | Export or IMAP transfer depending on the provider |
AWS, DigitalOcean, Linode, Vultr and self-managed servers | Depends on the stack | We need to see what is running; custom applications are quoted individually |
Shopify and hosted e-commerce platforms | Rebuild required | Product and customer data exports; the storefront itself is rebuilt on WooCommerce |
Plan | Price | What you get | Built for |
|---|---|---|---|
Shared Cloud | $7.99/mo, renews $12.99 | 2 sites, 10 GB NVMe | Brochure sites, small business sites, low-traffic WooCommerce |
VPS | From $79/mo | Guaranteed cores and memory, cPanel and WHM included | Busy sites, several client sites, line-of-business applications |
Dedicated Cloud | From $65.95/mo | 2 to 8 Intel cores, up to 1 TB NVMe | High-traffic sites, multiple applications, heavier workloads |
Your current host, how many sites, roughly how large, how many mailboxes, and anything unusual. We review it and come back with the scope and any surprises before you commit to anything.
Give us access or a backup, and our team moves sites, databases, mail, cron jobs, redirects and SSL. Your old host keeps serving live traffic the entire time.
Everything runs on the new server at a temporary URL. Click through it, submit a form, run a test order, check a mailbox. Nothing has changed for a single visitor yet.
We update DNS at a quiet time, issue SSL and watch the first 48 hours. Once it is proven, you let the old plan run out rather than paying into another term.
Real customer reviews. LiberationTek is rated 4.9 out of 5 on Google and 4.7 out of 5 on Trustpilot (September 2026).
Liberation can transfer your website content from most site builder platforms.
Migration is free on most plans. Our team reviews what you are running — how many sites, how large the databases are, how many mailboxes and anything unusual in the stack — and confirms the scope before anything starts. Larger or more complex moves, and rebuilds from platforms with no usable export, are quoted individually so there are no surprises on either side.
A single small site is usually an afternoon. A business site with mail on a custom domain is typically a day, and most of that day is waiting for DNS to propagate rather than anyone actively working. Larger accounts with many sites or big databases take longer, and the review tells you which of those you are before you commit.
No. Your current host keeps serving live traffic the entire time. Your site is built on our server at a temporary address, you review it there, and only once you are satisfied do we change DNS. There is no window where the old site is gone and the new one is not ready, because both exist at once.
Yes, and it is the part worth getting right. We transfer mailboxes with their folder structure and message history over IMAP from most providers, including Google Workspace, Microsoft 365, Zoho and cPanel mail. MX records are cut over at a quiet time so nothing bounces. Calendars and contacts export separately and we handle those too.
Not if the migration is done properly. Your URL structure, redirects and rewrite rules move with the site, so existing links and indexed pages keep resolving. Ranking losses after a migration almost always come from URLs changing without redirects, or from a site going offline long enough to be recrawled while broken. We avoid both by design.
Not as a transfer, and we will say so before you pay anything. Neither platform offers an export that recreates a working site somewhere else — that is a deliberate design decision on their part, not a technical accident. What we can do is rebuild the site on WordPress, carrying over your content, images and structure, and quote that as a build rather than a migration. The same is true of hosted e-commerce storefronts, where product and customer data export but the storefront is rebuilt.
No, and please do not. Keep the old plan running until the new one is proven, then let it lapse at the end of its term. Anyone advising you to cancel before the move is making their own job easier at the cost of your safety net.
We watch the first 48 hours after DNS changes — mail flow, SSL, error logs and form submissions — because that is when migration problems surface. If something needs fixing, we fix it. Your old host is generally still live at that point as well, which means rolling back is a DNS change rather than a crisis.
Migrations have a bad reputation, and it is earned. But the failures are not random — they are the same five things, every time.
This is the big one. The old host is cancelled to save a month, the move hits a snag, and now there is no working copy of the site anywhere and no way back.
Keep the old plan until the new one is proven. It costs one more month and removes the entire category of disaster.
A website has one A record and a company has a dozen other records doing quiet, essential work. MX for mail. SPF, DKIM and DMARC for whether that mail is believed. CNAMEs for your help desk, your booking tool, your email marketing platform.
Move the A record alone and the site comes up fine. Mail stops two hours later, and nobody connects the two events.
If the new platform produces different URLs and nothing redirects the old ones, every link anyone has ever made to you now lands on a 404, and search engines drop the pages.
Redirects and rewrite rules have to move with the site. That is the difference between a migration and a relaunch.
Forwarding mail to a new address is not a migration. The history stays behind, the folder structure stays behind, and the day someone needs a three-year-old invoice, it is on a server nobody pays for any more.
Mailboxes transfer over IMAP with their folders and history intact, and the MX cutover happens at a quiet time.
Most migration problems do not appear at the moment of switching. They appear when the first contact form is submitted, the first scheduled task is due to run, or the first customer replies to an order confirmation.
That is why we monitor the first 48 hours rather than declaring it done when the homepage loads.

Two things, before you pay anything.
Wix and Squarespace sites cannot be migrated. Neither platform offers an export that recreates a working site elsewhere. That is a deliberate product decision on their part, not a technical accident, and it is the clearest argument there is for owning your platform. What we can do is rebuild on WordPress, carrying your content, images and structure across, and quote it as a build rather than pretending it is a transfer.
Sometimes you should stay where you are. If your current host is working, your renewal is fair, and nothing about the arrangement bothers you, moving is churn rather than progress. We will say so. We would rather have the conversation than the cancellation three months later.
Email migrations deserve their own paragraph because they are the ones people remember.
The order is what matters. Create the new mailboxes first. Transfer the mail into them over IMAP, with folders and history, while the old server still receives everything. Only then change the MX records, at an hour when almost nobody is sending.
Done that way, the worst case is a message arriving in the old mailbox during the cutover window, which we collect afterwards. Done in the wrong order, mail bounces and senders get a delivery failure with your company name on it.
None of this is required, but having it to hand turns a two-day back-and-forth into a single conversation.
Who your current host is, and what plan you are on. The renewal date matters too — it tells us how much runway we have and whether you are about to pay into another term unnecessarily.
How many websites are on the account. Not just the main one. Old microsites, a staging copy someone made in 2022, a landing page for a campaign that ended — these turn up constantly and each one is a decision about whether it moves or gets retired.
Where your domain is registered. Often it is not the same company as your host, and surprisingly often nobody currently at the business knows the login. Finding that out now is much better than finding it out on cutover day.
How many mailboxes there are and where they live. Including the shared ones. The info@ and accounts@ addresses that three people check are the ones most likely to be forgotten and most painful to lose.
Anything custom. A booking system, a members area, a payment integration, a plugin somebody had built. Custom work is not a problem; custom work nobody mentioned until it broke is a problem.
Who needs to approve the switch. Migrations stall far more often on someone being unreachable than on anything technical.
If you do not have all of it, send what you have. Part of the review is working out the rest, and we would rather start the conversation than wait for a perfect inventory that never gets compiled.
Migration is free on most plans. We review what you are running and confirm the scope in writing before anything starts.
Larger accounts, unusual stacks and platform rebuilds are quoted individually — not to add a fee, but because pretending a forty-site account is the same job as a brochure site is how migrations end badly for both sides.
Send us your current host, roughly how many sites and mailboxes you have, and anything you already know is odd about the setup. We will come back with the scope, the timing and the honest answer about whether it is worth doing.
Related pages: Transfer your website · Transfer your email · Switching providers · Shared Cloud hosting · VPS hosting · Dedicated Cloud · Reseller hosting · Liberation Email · All comparisons
Migration scope, timing and pricing are confirmed in writing after our review and before any work begins. Free migration applies to most plans; complex moves and platform rebuilds are quoted individually.