Many businesses get their first website up on Wix or Squarespace because it is quick. Others have been on WordPress for years, with a design that no longer matches the business and a plugin list nobody wants to touch. The site still works, until it does not: it is slow on a phone, hard to edit, expensive to keep, or unable to connect to the booking tool, CRM or app you now need.
Moving off that platform is one of the most common website projects I take on, and one of the easiest to get wrong. Treat it as a visual refresh and you can lose search traffic, break enquiry forms, knock out business email, or spend weeks recreating content you already had. This article covers what to protect, what to export, how to choose what you move to, and how I run the project.
Why businesses leave a builder or an old WordPress site
The reasons are usually specific, not aesthetic.
You do not really own the site. On a builder, your pages, design and sometimes even your images live inside that product. Export options are limited. If you cancel the plan, you may be left with a ZIP of messy HTML, or nothing you can use. That is a weak position when you want to change direction.
The site has hit a ceiling. Builders are fine for a brochure. They get awkward when you need a real enquiry workflow, a members area, a booking calendar that matches how you work, or a connection to a system you already run. Third-party widgets pile up, and the site gets slower.
It is slow, or it looks wrong on a phone. Visitors leave before they read. Page builders and heavy plugins are a common cause on older WordPress sites. Speed is not a nice extra; it is whether anyone stays long enough to contact you. That has to be fixed in the new site, not promised as a later patch.
Nobody dares to update it. The WordPress site has been patched by several people, the plugins conflict, and the person who built it is gone. Every change feels risky, so the content goes stale.
You want the accounts in your name. Domain, hosting, analytics and the CMS should belong to the business, not to a previous freelancer's login or a platform plan you cannot leave.
This is a rebuild, with a plan to keep what already works
You are not putting a new coat of paint on the old product. You are building a new site, moving the content that still matters, pointing the same domain at it, and sending old addresses to the right new ones so Google and existing links do not die.
The search side of that job has its own sequence: inventory every URL, decide which pages to keep, merge or drop, build a redirect map, test on staging, then watch the weeks after launch. I walked through that in redesigning your website without losing your Google rankings. The rest of this article is the work around that: access, content, email, forms, platform choice and launch.
What you must not break
The domain and business email
The domain is the durable asset. The new site should use the same one you already have, unless you have a strong reason to change it. Changing the domain throws away type-in traffic and makes the search work much harder.
Email is the part people forget. If the team's inboxes sit on the same domain as the website, a careless DNS change can take email down for days. Before anything moves, I want to know where email is hosted (Google Workspace, Microsoft 365, the registrar, or the current web host) and I leave those records alone unless we planned to touch them. In most moves, only the website's DNS records change.
Enquiry forms and where leads go
List every form: contact, quote request, newsletter, application. Note where each one sends the message, whether anyone replies from that inbox, and whether you need to keep old submissions. The new site should land enquiries in a place someone actually checks, and you should test that path on staging, not on launch day.
Analytics, Search Console and ads
If the current site has Google Analytics or Search Console, keep the same properties where possible and update them for the new site. Ad landing URLs belong in the redirect map. Lose this history and you cannot tell whether the new site is doing better or worse.
Certificates and the www decision
Decide once whether the live site lives on www or on the bare domain, and redirect the other. Mix them up and you get duplicate content and messy certificates. SSL has to work on launch day, including on the redirected hostname.
What to export and prepare before anyone builds
A move is delayed by missing content far more often than by code. I would rather start late with a complete pack than start on time and wait two weeks for images.
A page inventory. Every public URL, including hidden landing pages, blog posts, PDF brochures and old campaign pages. Mark each one: move as-is, rewrite, merge into another page, or retire with a redirect.
The actual content, not a screenshot. Headlines, body text, team bios, service descriptions, prices you still want public, testimonials you have permission to reuse, and legal pages (privacy, terms). If the builder export is messy, paste the live text into a document and clean it there. Write down the pages the new site actually needs: home, services, about, contact, and any project or product pages you still want public.
Images and files. Original photos if you have them, not only the compressed versions the builder serves. Logos in a proper format, and PDFs people still link to. Check you have the rights to use the photos.
The URL list for redirects. Old blog slugs, mixed capitalization, trailing slashes, and any short links you used on Instagram or Google Business. This is the raw material for the redirect map.
Access, in the business's name. Login to the current site, the domain registrar, DNS, the current host, Google Search Console, analytics, and any form or newsletter tool. If those accounts still sit under a previous freelancer's email, recover them before the move.
You do not need a finished rewrite of every page on day one. You do need to know which pages exist and who will write the ones that change.
Choosing what you move to
This is the decision that should happen before design, not after.
WordPress is the right landing place when the main job of the site is to explain the business, publish updates, and let your team edit pages without me. I build that kind of site with a clear structure, and with Elementor when the team wants to change content themselves. AgriDev is an example: a WordPress site for an agricultural development organization, with home, about, services, projects, blog and contact pages the team can edit, plus an enquiry form and caching so the image-heavy pages stay fast. Alpha Green is a similar shape for a grower of lettuce and leafy greens: home, about, production, products and blog, with an enquiry form.
A custom site, usually in Next.js, is the better fit when the site is closer to software: logins, a dashboard, a catalogue with rules, or a tight connection to an app or a CRM. It can still have an editing interface for the pages you want to change, and it is the clearer choice when a builder already failed you because of those needs.
I do not pick a platform out of habit. I wrote a fuller comparison in WordPress with Elementor or a custom Next.js site. On a move, the useful questions are: who will edit the site next year, what it has to connect to, and whether you are leaving because of design or because of a real product limit.
If you also need a logged-in tool for staff or clients, say so early. The public site and the web app can share a backend so you are not copying records between systems.
How I run the move
The work sits under website development. In outline it looks like this:
- Access and inventory. We confirm ownership of the domain and accounts, list every URL, and agree which pages are in the first launch.
- The new site, on staging. Design and build happen on a staging address, with the real content as it becomes ready. You review pages there, not as placeholder text.
- Redirects, forms and integrations. The redirect map is built from the inventory. Forms are tested. Analytics and Search Console are connected. If the site needs Arabic and English, both languages are designed in from the start, including right-to-left layout, rather than added later.
- Launch. DNS points the domain at the new site, redirects go live, SSL is checked, and we immediately test the homepage, key landing pages, forms and a sample of old URLs. Email records stay untouched unless we planned a change.
- The weeks after. We watch Search Console for crawl errors and unexpected drops, fix what appears, and only then talk about pages left for later.
You own the code after the final payment. On a new project, the repository, domain and hosting accounts are set up in your name.
Timelines and what actually drives the work
I do not publish prices here. The scope of the new site decides the quote, and the quote is fixed once that scope is agreed.
Time is usually driven by three things: how many pages and posts you are moving, how much of the content needs to be rewritten, and whether the new site is a straightforward brochure or a custom web app. A tight site with a handful of pages and clean content moves faster than a ten-year WordPress blog with hundreds of URLs and missing images. The platform you leave matters less than how tidy the inventory is.
If you have a deadline, say so at the start so we can cut the first version to the pages that have to be ready, and move the long tail of older articles afterwards, with redirects in place.
What to send me if you want this done
A short note is enough to start: the current URL, what is frustrating you, whether you want to stay on WordPress or are open to a custom build, and any deadline.
Email hello@eliechaaban.com or use the contact section, and we can go through the inventory on a call and agree a first version that gets you off the old platform without losing what already works.