Migrate from Framer

Platform

Last updated

Move a published Framer site into Ploy as code that you can clone and keep building on.

Framer doesn't support export (see Can I export my website to HTML and self-host it?).

Ploy rebuilds your public pages as code in a Ploy site, imports your CMS collections into PloyDB, and gives you the source through Git or GitHub on every plan. It is a rebuild, not an identical copy, so plan to review every page before you switch. Ploy can also enhance your existing Framer site design if you are not happy with it.


Before you start

  • Your site is published and public. Pages must be reachable over HTTP(S) without signing in. Pages behind a login or password need separate work.
  • For CMS content, have your Framer project URL and an API key ready. Ploy asks for them in a secure form, so they stay out of the chat. Creating the database and tables needs a workspace owner or admin.
  • Keeping the code works on every plan. Clone it with Git, or sync it with GitHub through the Ploy CLI. See Step 4.
  • Check your credits. Building uses AI credits, and larger sites use more. Before a full build, open Settings, then Organization, then Usage. See Credits.
  • Connect Google Search Console. Connect it in Integrations on any plan. Ploy's Agent then sees which of your pages get search traffic and whether they are indexed, so it can map redirects in Step 5. See Analytics.

Step 1: Import the pages from your URL

In a chat, give Ploy's Agent your published address and ask it to rebuild your site on Ploy:

"Rebuild my Framer site at www.example.com on Ploy. Show me the page plan before you build."

Ploy's Agent inventories your site and recommends which pages to rebuild and which to keep on your current host. It shows you its plan and starts building right away, unless you ask to review the plan first. You can change what moves at any time in the chat. You can also run the Rebuild your site on Ploy Ploybook.

On a large site, Ploy's Agent builds your key pages first while Framer keeps serving the rest. It publishes only with your OK, and nothing changes on your current site until you approve the switch.

When the pages are built, review content, images, links, layout and interactions on desktop and mobile. Ask Ploy's Agent to correct anything missing. See Import an existing website.

Step 2: Import your CMS collections

Ask Ploy's Agent to bring your Framer CMS into PloyDB:

"Import my Framer CMS content from www.example.com into PloyDB."

  1. Ploy opens a secure form for a one-time connection using your Framer project URL and API key.
  2. Ploy analyzes the source and shows the collections, fields and record counts it finds. Nothing is written during this analysis.
  3. Choose every collection or a subset, and a new or existing database. Collections become PloyDB tables with typed fields.
  4. Ask Ploy's Agent to build list and detail pages from the new tables.

A few things to know:

  • Images finish in the background. Records start with the Framer image URLs. A background job then copies the images into your asset library. If an image can't be reached, it keeps its original URL.
  • A re-import is not a sync. Importing again creates fresh tables and doesn't merge with the earlier import.
  • Records don't carry routes. URL paths, templates, metadata, structured data and redirects belong to the page rebuild. Check them before you publish.

See Migrate CMS Content to PloyDB.

Step 3: Rebuild what doesn't transfer

An import is not an identical copy. Private pages, dynamic features, forms and live data connections may need separate work. Go through this list before you switch.

  • Forms. Forms may need separate work. Ask Ploy's Agent to check each form and rebuild any that don't work. Forms built into a Ploy site capture submissions automatically, and you choose who gets an email when one arrives. See Form Submissions.
  • Animations and interactions. Compare each rebuilt page with the original, including scroll effects, hover states and transitions. Ask Ploy's Agent to recreate the ones that matter.
  • Code components, plugins and embeds. Check that each one works on the rebuilt page. Ask Ploy's Agent to rebuild or replace the ones that don't.
  • Private pages and live data. Plan these separately. You can keep them on Framer for now with routing (see Step 5).

Step 4: Keep the code

Your site's full source is yours to clone, edit and push. Cloning with Git and syncing with GitHub through the Ploy CLI both work on every plan, including Free. Choose either option, or both.

Clone with Git

  1. Install the Ploy CLI and sign in.
  2. Run ploy site git clone <directory> to get your site's full source.
  3. Edit locally and push changes back with plain Git. GitHub is not required.

You need the Member role or higher in the workspace. See Push code with Git.

Sync with GitHub

On any plan, run ploy site code-sync init with the Ploy CLI and follow the printed setup steps. On a paid plan, a workspace owner or admin can instead open Workspace Settings, select Developer, and connect Ploy Code Sync. Edits from Ploy's Agent then commit to the site's GitHub repository, and your team's commits come back into Ploy when you sync from GitHub. See Code Sync with GitHub.

Step 5: Switch traffic without losing URLs

Before you switch DNS, go through the Migration Readiness Checklist.

  • Keep your paths. Where you can, keep each URL the same on Ploy. For any URL that changes, add a 301 redirect in Path routing. Ploy's Agent can use your Search Console data to find the URLs that need one.
  • Carry over your metadata. Check that each page keeps its title tag, meta description and canonical URL.
  • Move in stages if you like. Once your domain points at Ploy, you can proxy the pages you haven't moved to your Framer site's *.framer.website or *.framer.app address. Use the Everything else row in Path routing for everything Ploy doesn't serve, or add paths for chosen pages. You can keep this mix for as long as you need. See Proxy to Framer.
  • Publish when you're ready. Ploy's Agent checks the pages, helps you switch over and publishes only with your OK. The Launch Checklist covers the full cutover.

What transfers and what doesn't

Part of your siteWhat happensWhat to check
Public pages: layout, copy, images, linksRebuilt as Astro, React and Tailwind codeReview every page on desktop and mobile. It is not an identical copy.
CMS collections and fieldsImported into PloyDB tablesNeeds your Framer project URL and API key. A re-import is not a sync.
CMS imagesCopied to your asset library in the backgroundImages that can't be reached keep their original URL.
URL paths, metadata and redirectsSet during the page rebuildThe CMS import doesn't carry them. Check before you publish.
FormsMay need rebuildingTest each form. Forms built on Ploy capture submissions.
Animations and interactionsNeed reviewRecreate the ones that matter.
Code components, plugins and embedsNeed reviewRebuild or replace any that don't work.
Private or password-protected pagesNot imported from the URLRebuild separately or keep them on Framer with routing.
Dynamic features and live data connectionsSeparate workPlan each one with Ploy's Agent.
Source codeYours on every planClone with ploy site git clone or sync with GitHub.

When another route fits better

Ploy is a platform. You keep building the site with Ploy's Agent, publish it on Ploy, and take the code with you on any plan. That isn't the right fit for everyone.

  • You want a standalone project and no platform. A converter may fit better. For example, Deframer is an independent tool that converts a published Framer site into a Next.js or TanStack Start project in TypeScript that you download and host yourself. Its article Can you export code from Framer? compares rebuilding by hand, an HTML snapshot, a converter and a reverse proxy.
  • You only need an archive. A static HTML snapshot saved with a third-party tool can be enough. It is compiled output, not a project to keep editing.
  • Nobody on your team needs the code. Staying on Framer may be simplest.

FAQ

Does Framer let me export my site's code?

No. Framer doesn't support export. Ploy rebuilds the site as code you can clone on any plan.

Is the rebuilt site an identical copy?

No. Ploy rebuilds your public pages as code, and you review each page before you switch. Forms, interactions, private pages, dynamic features and live data may need separate work.

Do I need a paid plan?

Not to get the source code. ploy site git clone works on every plan, including Free. GitHub Code Sync set up through the CLI is free too. Custom domains need a paid plan (Starter or higher). Building with Ploy's Agent uses AI credits on every plan. See Credits.

Does my Framer CMS come over?

Ploy can import your Framer CMS collections and typed fields into PloyDB tables after a one-time connection with your project URL and an API key. Check the imported records, since a value Ploy can't read is left empty. A re-import creates fresh tables and is not a sync.

Can I keep part of my site on Framer?

Yes. Once your domain points at Ploy, proxy the pages you haven't moved to your Framer site's address with the Everything else row or paths in Path routing. See Proxy to Framer.