← Pressferry
DocumentationSupport

How Pressferry works

1. Source

From your site: type its address and click Read site. Pressferry reads the public WordPress API straight from the plugin: post types, categories, tags, authors, posts and pages with their featured images, Yoast titles and descriptions and ACF fields (when the site shows them in the API). Only published content is public. Some security plugins and hosts block this; the plugin then says so.

From an export file: in WordPress, Tools > Export > All content > Download Export File, then pick the .xml (or a .zip with it inside) in the plugin. This always works and includes drafts and scheduled posts, Rank Math fields and the media library's alt text. The file is read inside the plugin window and never uploaded anywhere.

2. Map

Each post type becomes a collection. Pick which ones, name the collection, set the page path you'll use for its CMS page (like /blog), and choose whether drafts come across as Framer drafts. Under Fields, switch fields on or off and rename them; custom fields can be plain text instead of their detected type. Categories and tags can be their own collections (multi reference fields), an option field (one value, the primary category) or text. Authors can be a collection with bio, avatar and website, or just the name.

3. Dry run

The Review tab shows what an import will add, update, leave alone and skip in each collection, which fields get created, how many images get copied, what needs a look (forms, page builder shortcodes, embeds other than YouTube and Vimeo, blocks from other plugins) and which links still point at pages you aren't importing. Download it as a CSV. Nothing is written yet.

4. Import

Import asks you to confirm, then creates the collections and fields, copies images into Framer, writes authors and terms first and then posts with their references. If you already have a CMS page for a collection, its path is used for links and redirects. If a collection with the same name exists, Pressferry adds to it; a field with the same name and another type is left alone and named in the warnings. Slugs from WordPress are kept unless another item already uses them.

5. Redirects

Every post whose address changes gets a redirect from its old WordPress path to its new Framer path. Add them to Framer in one click (redirects need a Framer plan that includes them), or download the CSV, which Framer's Redirect Sync plugin imports. Posts that used plain addresses (?p=123) can't be redirected one by one: add a single /?p=* redirect to your blog page in Framer's site settings.

Run it again

Each imported item remembers where it came from. Run the dry run again later: changed posts update in place, unchanged ones are skipped, new ones are added. Posts deleted in WordPress are not deleted in Framer.

Undo

Undo the last import removes the items and fields it added and its redirects, and puts back the previous content of items it updated (in the same browser). Framer doesn't let plugins delete collections, so empty collections stay; delete them by hand if you like.

License

Paste the license key from your email in the Plan tab. One seat works on two Framer accounts and every project and site you migrate. Support: hello@greatwork.company.