Import & Export

Move content between environments with RailsPress import and export workflows for posts and CMS content.

Configuration

Post import/export works out of the box. Some workflows in this guide require feature toggles:

  • config.enable_cms for CMS content transfer.
  • config.enable_post_images to include post header images.
  • config.enable_authors to include author metadata.
  • config.enable_api if you run imports through assistant/API tooling.
config/initializers/railspress.rb
Railspress.configure do |config|
  config.enable_cms
  config.enable_post_images
  config.enable_authors
  config.enable_api
end

See Configuration and Agents & API setup for details.

When to Use Import/Export

Import/export is useful when content needs to move between environments, teams, or projects without rewriting everything by hand.

Common cases:

  • Staging to production: Move approved content into your live environment.
  • Bulk migrations: Bring a large set of posts into RailsPress.
  • Backups: Keep a portable copy of your published content.
  • Content handoffs: Share content archives between projects.
Note

RailsPress has separate import/export workflows for posts and CMS content groups. Choose the matching workflow for the content type you are moving.

Exporting Content

Use export when you need to package content from the current environment.

01

Open the export screen

In admin, go to the relevant export area for posts or CMS content.

02

Choose your export type

Select the content you want to include and start export.

03

Download the file

Save the exported file in a safe location so it can be imported into another environment.

Screenshot: Export screen with options and completed download

Importing Content

Use import to bring content files into the current environment.

01

Open the import screen

Navigate to the matching import area (posts or CMS transfer).

02

Upload your file

Drag-and-drop or browse for the exported file package.

03

Run import and review status

Complete the import and read the result summary (created, updated, restored, or errors).

Important

Always test imports in staging before production, especially when replacing large sets of existing content.

Working with AI Assistants

If your team uses an AI assistant to draft or import posts, use the Agents & API page in admin to issue a short-lived agent key. Share only the one-time setup instructions, not long-lived credentials.

  1. Open Agents & API in admin.
  2. Create a new Agent Key for the assistant session.
  3. Copy the one-time instructions into your assistant tool.
  4. Revoke the key when the task is complete.

Verifying Results

After import, verify both admin data and live page output.

  • Check record counts in admin lists.
  • Open a sample of imported items and confirm text, images, and relationships.
  • Review key frontend pages to confirm content renders as expected.
  • Validate tags/categories and media assets are attached correctly.
Tip

Keep a small “golden” content sample that you import first every time. It helps quickly confirm your workflow before larger imports.

Common Pitfalls

  • Wrong environment: Accidentally importing into production instead of staging.
  • Old file versions: Importing outdated exports after new edits were made elsewhere.
  • Missing media review: Assuming images are attached without checking spot samples.
  • No rollback plan: Running large imports without a backup/export snapshot first.

When in doubt, export first, then import. This gives you a reliable fallback point.