Migrate CMS Content to PloyDB
Bring posts, case studies, products, resources, and other structured content from your existing CMS into PloyDB. Paste your site URL, review what Ploy finds, then import it into tables you can edit and use across your site.
Start in chat with a content URL:
"Import my CMS content from acme.com/blog into PloyDB."
Ploy analyzes the source before writing anything. You can review the collections, fields, and available record counts, choose what to bring over, and decide whether the content should land in a new or existing database.
How It Works
- Paste your site URL in chat. Ploy attempts to detect the CMS, locate its content, and identify the available collections. A homepage or a more specific content URL can both work.
- Review what Ploy finds. Before importing, Ploy shows the detected platform, collections, fields, and available record counts. Nothing is written during this analysis.
- Choose what to import. Bring over every detected collection or select only the content you need. You can create a new database or add the new tables to an existing one.
- Build with the imported data. Once records begin landing, ask Ploy to create list pages, detail pages, filters, and other experiences backed by the tables.
You can start with your main site URL. Ploy will attempt to locate the CMS content and may ask for a more specific section if it cannot find it automatically.
How Content Maps to PloyDB
Each repeating collection becomes structured data you can manage in the Ploy dashboard:
| Existing CMS | PloyDB |
|---|---|
| Collection or content type | Table |
| Content item | Record |
| Field or property | Column |
| Rich-text body | Render-ready long text |
| Image | Source URL first, then a workspace-hosted asset after processing |
Common fields such as title, slug, body, author, published date, category, and cover image keep their structure wherever the source makes it available. Complex or proprietary embeds do not always have a direct equivalent, so spot-check media-heavy content after the import.
Supported Sources
| Source | What to Expect |
|---|---|
| WordPress | Uses a public content URL with no connection step. Imports posts, pages, and custom post types. |
| Squarespace | Uses a public content URL with no connection step. Imports blog, store, and portfolio collections. |
| Sanity | Public datasets can import from a content URL. With a connected token, Ploy can import the project directly without a site URL. |
| Webflow | Requires a one-time secure connection, then imports CMS collections and typed fields. |
| Framer | Requires a one-time secure connection using the project URL and an API key, then imports CMS collections and typed fields. |
| Wix | Requires a one-time secure connection, then imports the site's user-built CMS collections. Wix app collections such as Stores, Bookings, and Coupons are skipped. |
| Notion | Requires a one-time secure connection. Shared Notion databases become PloyDB tables; relation and rollup properties are skipped. |
Before You Import
- Owner or admin access is required. Creating the destination database and tables requires a workspace owner or admin.
- A re-import is not a sync. Running the import again creates fresh tables and does not deduplicate against a previous import. To refresh a source cleanly, use a clean database rather than treating re-import as an incremental update.
- One unreadable cell does not drop the record. If Ploy cannot read or convert one value, it leaves that cell empty. The database card marks the run as partial so you know to inspect the imported data.
- Images finish in the background. Records initially use the source image URLs. After the content lands, a background job attempts to copy images into the workspace asset library and update the records. If an image cannot be reached, it keeps its original URL.
Imports run in the background. Rows appear in the database as they land, and the database card shows the import status and flags partial or failed outcomes.
Build New Pages from Imported Content
Once the content is in PloyDB, use it to create:
- Blogs with an index, one dynamic post template, and optional tag or author archives.
- Resource libraries with filters for topic, format, audience, or other imported fields.
- Case study and changelog collections that stay current as records change.
- Directories and catalogs built from products, people, events, or other repeating records.
- New content experiences that reuse the imported data without rebuilding every entry by hand.
For example:
"Build a resource library from the imported Resources table, with a page for each item and filters for topic and content type."
Ploy builds one reusable template for each detail-page layout. Adding or editing a record then updates the content without creating a separate hardcoded page for every item.
FAQ
Do I need to know which CMS my site uses?
No. Give Ploy your main site URL or a content URL. It will attempt to detect the CMS and locate the available collections. If nothing is found, tell Ploy which platform you use or where the content lives.
Which URL should I give Ploy?
Start with your main site URL or provide a more specific section such as /blog, /resources, or /news. A specific content URL can help, but it is not required.
Can I choose only certain collections?
Yes. Ploy analyzes first and shows the collections it found. You can import all of them or choose a subset.
Can I import into an existing database?
Yes. By default, Ploy creates a new database named after the source. You can instead choose an existing database and add the imported collections as new tables.
Does re-importing update my existing tables?
No. A re-import creates fresh tables and does not deduplicate or sync against an earlier import. Use a clean database when you need to refresh the source.
What permissions do I need?
You must be a workspace owner or admin to create the destination database and tables.
What happens when one field cannot be imported?
Ploy keeps the record and leaves the unreadable cell empty. The database card marks the run as partial so you can inspect the imported rows.
Do I paste an API key into chat?
No. When a source requires a connection, Ploy opens a secure form. The credential is validated and stored encrypted for the workspace, outside the chat transcript.
What happens to images and embedded media?
Images initially use the source URLs, then a background job attempts to re-host them in the workspace asset library. If an image cannot be reached, it keeps its original URL. Common video links can carry over, but complex or proprietary embeds may need review after import.
Will importing preserve my URLs and SEO?
Importing records does not by itself preserve routes. URL paths, templates, metadata, structured data, and redirects belong to the page-recreation phase. Review those before publishing the migrated pages.
What's Next?
- Understand the data model — Database covers tables, records, access keys, and editing.
- Run a blog — CMS & Blogging covers database-backed publishing workflows.
- Build the pages — Site Builder explains pages, sections, and the design system.
- Plan a cutover — Launch Checklist covers routes, redirects, SEO, and publishing checks.