Can my site be moved? A go or no-go check to run before you commit to anything

By Ranjit Bhinge, founder of Blur Studio · Updated · 11 min read

Short answer: Almost every public website can be moved, but not every part of it moves the same way. The pages usually can. Forms, online stores, member areas, languages, and anything that depends on a plugin or live data usually need separate work. Before you commit, list those parts, score them with the table below, and test the move on a copy while your live site stays untouched. Moves away from Wix (a website builder that hosts everything on its own servers) are the hardest, because Wix does not let you take a built site to another host.

Ranjit Bhinge

You want to know whether your website can be moved at all, and what could break, before you spend money or touch your domain.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Can your site be moved? Yes in most cases, with one condition: you should know which parts will not come across before you start. A website has two layers. The first is what visitors read: pages, text, images and menus. The second is what the site does: forms, bookings, checkout, logins, languages and tracking. Tools and people move the first layer well. The second layer is where moves fail, so that is where this page spends its time.

This is a how-to for owners and for agencies who run client sites. It gives you a feasibility check (a list of questions that decides if a move is safe), a score, a copy test, and clear "stop" signs. One option for the actual move is Ploy, an AI platform that builds and hosts business websites and can rebuild a site from its public web address. It is one option among several, and the check works the same whichever you pick.

This page may contain affiliate links from which Blur Studio earns commissions.

Step 1: can your platform let the site leave?

Start with where the site lives today, because some platforms limit what you can take. This is the first go or no-go gate. These rules come from each vendor's own help pages, as of November 2026. Check the current page before you decide, because platforms change export rules.

Current platformWhat the vendor lets you takeWhat stays behind
WordPress (a free publishing system many sites run on)An XML export of posts, pages, comments, categories, tags and custom fields from Tools, then Export. Plugins can make CSV files.Plugin settings, theme layout, and forms that depend on plugins. WordPress's own export page does not promise the image files themselves, so copy your media library separately.
Webflow (a visual website builder)On paid Workspace plans: HTML, CSS, JavaScript and assets as a zip. CMS content can be exported as CSV.CMS pages come out empty, plus ecommerce, user accounts and localized content. Site search and forms do not work on an exported site.
Framer (a design-led website builder)Framer's help page says it does not offer HTML export for self-hosting.The built site. You can move by rebuilding from the public pages.
WixNo export of a built site. Wix says the site needs to be hosted and operated on Wix's servers. You can keep a domain registered elsewhere.The built site. You can keep the domain and rebuild the pages elsewhere.
Squarespace (a hosted website builder)A partial XML export meant for WordPress: one blog page, up to 1,000 comments per post, some page types.Several page types (album, cover, index, calendar, portfolio, store), product and video blocks, drafts and custom CSS.

The pattern: if the vendor lets you export code or content, you can move with a copy. If it does not, the move is a rebuild from the public pages. A rebuild is fine, but it means every page is new work to review. Ploy describes its own migration this way: its docs call it "a rebuild, not an identical copy", and nothing changes on your live site until you approve the switch. For the details of how that works, read how Ploy site migration works.

Step 2: the feasibility checklist

Go through each line and write down the answer. This takes about an hour for a small site, and it is the cheapest hour in the whole project.

  1. Every URL. Crawl your site or export the sitemap (the list of pages you give search engines). Count the pages. Mark which ones get traffic or links, using Google Search Console (Google's free tool that shows how your site appears in search).
  2. Forms. For every form, write down who gets the email, where the entries are stored, and whether past entries are in a place you can export. Do not assume past entries come across.
  3. Plugins and apps. List booking tools, chat widgets, memberships, calendars, maps, pop-ups and anything pasted in as an embed or code.
  4. Store or payments. If you sell products, the store will probably stay where it is. Moving a store is its own project.
  5. Logins and private pages. Password-protected pages cannot be read from a public address, so they will not be copied by any tool that works from your live URL.
  6. Languages. If you have versions in more than one language, write down the address pattern for each and whether each page points to its translated twin.
  7. Address pattern. Note whether your page addresses end in a slash and whether they use dates or folders. Changes here are the main cause of lost rankings, so you will need a redirect list for anything that changes. See keeping rankings when you move a site.
  8. Tracking and scripts. Analytics, advertising pixels, cookie banners. Write down the IDs now. They are easy to lose.
  9. Email records. Find out where your domain's DNS (the settings that tell the internet where your site and email live) is managed, and who has the login. Email records must not be touched. The page on pointing a domain without breaking email covers this.
  10. Who owns the logins. Registrar (where the domain was bought), DNS host, current website platform. A move stalls more often on a missing password than on a missing feature.

Step 3: what a rebuild tool says it can and cannot carry

Here is Ploy's own wording, from its migration pages as of 21 November 2026. Use it as a model for what to ask any tool or freelancer.

ItemWhat Ploy's docs sayYour action
Pages and textRebuilt from your published address on Ploy's design system. Review every page on desktop and mobile.Plan to read each page.
FormsMay need separate work. The WordPress guide says a migration report shows where each form sends email and where past entries stay.Rebuild and test each form. Export old entries yourself.
Plugins, shortcodes, embedsMay need separate work.Decide what to replace or drop.
Private or password pagesMay need separate work.Handle by hand.
Animations, custom code, live dataMay need separate work (Framer and Webflow pages).Decide what you can live without.
Stores, memberships, languages, structured dataThe WordPress and Webflow migration pages do not describe them.Ask Ploy before you commit. Do not assume yes.
URLs and redirectsKeep paths the same where you can, and add 301 redirects (permanent forwards) for any that change. Ploy tells you to group redirects into shared rules and contact support if you need more than 20 rules.Build the redirect sheet first.
Old sitemapDoes not carry over. Ploy builds a new one.Submit the new one in Search Console.
CostMoving from a URL uses AI credits, and bigger sites use more.Check your credit usage in Ploy's settings before a full build.

The pattern is useful beyond Ploy. Every honest tool will have a "may need separate work" list. If a vendor or freelancer says everything moves, ask for the list in writing.

Step 4: score it

Give each item a score. The numbers are my own rule of thumb, not an industry standard, so adjust them to your site.

Question0 points1 point3 points
Can the platform export?Yes, code or contentPartial exportNo export (rebuild only)
FormsNone or one simple form2 to 5 formsForms feed a CRM or payment
Apps and embedsNone1 to 34 or more, or a booking system
Store, members or loginsNoneSmall catalogCheckout, accounts or paid content
LanguagesOneTwo, with simple pagesThree or more, or per-language URLs
URL changesNone, same pathsUnder 10 percent changeMost addresses change
Pages that bring trafficUnder 20 pages matter20 to 100Hundreds, or a large blog
Who holds loginsYou have all of themOne is missingSeveral are with a former vendor
  • 0 to 4 points: go. A copy test and a normal cutover should be enough.
  • 5 to 10 points: go with a pilot. Move a handful of pages first and test the forms. Plan for separate work on the high-score items.
  • 11 or more: stop and scope. This is a project, not an import. Get a written scope from a freelancer or an agency before you commit. Parts of the site (a store, a booking system) may stay where they are.

A worked example with made-up numbers

A plumbing company has a WordPress site with 38 pages, 4 contact forms, a booking plugin, one language, and addresses it wants to keep. The owner has the domain login but not the hosting login.

  • Platform export: WordPress exports XML, so 0.
  • Forms: 4 forms, 1 point.
  • Apps and embeds: the booking plugin counts as 3 points on its own (a booking system), even with the chat and review widgets.
  • Store, members, languages: none, 0.
  • URL changes: none planned, 0.
  • Pages that bring traffic: 38 pages, of which 12 matter, 0.
  • Logins: hosting login missing, 1 point.

Total: 5 points. That is a go with a pilot. The to-do list: get the hosting login, decide to replace the booking plugin with a link to a booking page, test all 4 forms, and export the form entries to a spreadsheet. The same site with a store, French and English pages, and 400 changing addresses would score 12 or more, and the right answer would be a scoped project and a staged move, not an import button.

Step 5: test the move on a copy

The point of a copy test is that nothing about your live site changes. Do these in order.

  1. Freeze a baseline. Save a crawl of your current site: every address with its status. Export Search Console's top pages for the last 3 months.
  2. Run the import or rebuild on a private address. With Ploy, a first page is published to a ploy.build address, and migrations wait for your approval before anything changes on your live site. Other tools use a staging address (a private test copy).
  3. Compare page by page. Open the old and new page next to each other on a phone and a laptop. Check headings, links, images, and the phone number.
  4. Submit every form. Use a real test message and confirm it arrives at the right inbox, with the right sender name.
  5. Crawl the new copy. Compare its list of addresses to the baseline. Every old address should be either served at the same path, redirected, or on a list of pages you chose to drop. The Ploy readiness checklist uses this same three-way test.
  6. Check search settings. Make sure the copy has no leftover "noindex" setting (which tells Google to ignore a page) and no Disallow: / line in robots.txt (a file that tells search engines where not to look), but only after you have finished testing, so the copy is not found early.

The page on previewing a rebuild before you commit goes further on keeping a preview private and scoring it. This page is the earlier question: should you try at all.

Pass and fail rules

  • Pass: all pages that bring traffic exist on the copy with the same address or a mapped redirect; every form delivers; phone numbers, prices and legal text match.
  • Fail: any traffic page missing or changed in meaning, any form not delivering, or credits running out before the main pages are done.
  • Stop sign: you cannot recover a login you need, or the vendor cannot say in writing what it does not carry.

Your options, from least to most effort

  • Do it by hand. Free except for your time. Copy the content page by page, keep a redirect sheet, test. Best for under 20 pages.
  • A freelancer. Priced by quote or by the hour. Best when design or forms need custom work. Ask for the "what does not move" list in the quote.
  • An agency. Priced by quote. Best for large sites, stores, or several languages. Our page on migration tools and services compares the routes.
  • A rebuild tool. For a small business site made of pages and text, starting a copy test in Ploy is a quick way to see what a rebuild looks like before you decide. Ploy's plans as of November 2026: Free at $0 with 500 credits a day up to 2,000, Starter at $50 a month billed monthly, Pro at $300 a month billed monthly, Enterprise by custom quote. Annual billing is lower. A custom domain needs Starter or higher. Ploy's docs say unused credits do not carry over. Copy the current numbers from Ploy's pricing page, not from here.

When not to use a rebuild tool

  • Your site is mostly a store, a membership area or a booking system. These usually stay on their current host, and Ploy's docs say stores, accounts and apps can stay on your current host while pages move. Agencies that move many sites can read website migration as a service for agencies.
  • You need a pixel-for-pixel copy. A rebuild is a new version of each page, not a duplicate.
  • You have many private or password-protected pages. A tool that works from your public address cannot see them.
  • You have several languages and cannot confirm how the tool handles them. Ploy's migration pages do not say.
  • You need a signed statement about security reports or data export before you start. Ask Ploy for the current ones. Do not rely on a blog, including this one.

How I'd approach this

I would not decide on the tool first. I would run the checklist, score the site, and only then pick a route. If the score is low, a copy test costs you an afternoon and no money on the Free plan, so it is worth running before you spend anything. If the score is high, I would spend the money on a written scope instead, and I would keep any store or booking system where it is.

Here is a first-week plan. Day 1: collect the logins and crawl the site. Day 2: fill in the checklist and the score. Day 3: build the redirect sheet for any address that will change. Day 4: run the copy test, or ask two vendors for a written list of what does not move. Day 5: apply the pass and fail rules and decide. Do not change your domain in week one. Blur Studio also builds custom moves, such as sites with stores or booking systems, and finishes moves that stalled; you can see what that includes.

A closely related page covers the same ground from another angle: How to Move Your Site and Keep the Forms You Already Use.

For the next step, see How to Move Your Website One Section at a Time.

Related guide: How to Move Your CMS Content Into One Place.

Questions people ask

Can any website be migrated?

Most public sites can be moved or rebuilt. The limits are platform rules (Wix does not let a built site leave its servers, and Framer does not offer HTML export) and features that do not copy, such as stores, memberships, forms and plugins. Run the feasibility checklist to see which of those apply to you.

How do I test a migration without affecting my live site?

Move the pages to a private test address, leave your domain pointing at the old site, and compare page by page. Ploy's docs say nothing changes on your live site until you approve the switch. Submit every form and crawl the copy before you touch DNS. The preview guide explains the details.

Will I lose my Google rankings if I move my site?

Not necessarily, but a bad move can cost traffic. Keep addresses the same where you can, redirect any that change with a 301, submit a new sitemap, and watch Search Console. Nobody can promise results. See what to do if rankings dropped after a migration.

Do my form entries move with the site?

Do not assume so. Ploy's WordPress migration guide says its report shows where each form sends email and where past entries stay. Export old entries to a spreadsheet yourself, then rebuild and test each form.

Can I move a site off Wix?

You can keep your domain and rebuild the pages on another platform, but Wix says the site needs to be hosted and operated on Wix's servers, and its help page describes no export option. A rebuild from your public pages is the usual route. See moving off Wix or Squarespace.

How much does it cost to check if my site can be moved?

The checklist costs only your time. A copy test with a rebuild tool uses credits or a vendor's fee. Ploy's Free plan gives 500 credits a day up to 2,000, and moving from a URL uses credits, with bigger sites using more. Check your usage in Ploy's settings before a full build. Typical agency prices are in how much a website migration costs.

What should I get in writing before I commit to a move?

A list of what will not be carried over, who is responsible for forms and redirects, what happens to your old host and domain, and how to roll back. If it is a tool, ask for its current terms on data export and security reports. Do not rely on a sales page.

Is it safe to change my domain on the first day?

No. Test on a copy first, and plan the switch for a quiet hour with a way back. The steps are in how to move a client domain with zero downtime.

More in this topic: Websites: moving a site without losing traffic (5 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…