justbetter / statamic-replicator-transfer

1.0.0 2026-10-16 10:02 UTC

Requires

• php: ^8.4
• laravel/framework: ^12.0|^13.0
• statamic/cms: ^6.0

Requires (Dev)

• larastan/larastan: ^3.9
• laravel/pint: ^1.29
• orchestra/testbench: ^10.8|^11.0
• phpstan/phpstan-mockery: ^2.0
• rector/rector: ^2.3

MIT

• Bob Wezelman

Published on Packagist.org on 2026-10-16 10:47 UTC

README

Transfer Statamic replicator content between entries and environments.

Requirements

• PHP ^8.4
• Laravel ^12.0|^13.0
• Statamic ^6.0

Features

• From staging to production, no copy-paste required — Export replicator blocks from any entry and import them into any other entry, even across environments
• Your fields, your rules — Export and import actions only appear on the replicator fields you configure, keeping the Control Panel clean
• Inspect it, archive it, ship it — Transfers use a clean, human-readable JSON file you can version-control or pass between teams
• Non-destructive imports — Imported sets are appended to the existing replicator content, nothing is overwritten
• Works out of the box — Zero configuration needed; the actions appear automatically on any configured replicator field handle

Installation

composer require justbetter/statamic-replicator-transfer

Configuration

By default the export and import actions are available on replicator fields with the page_builder handle. Publish the config to add or change handles:

php artisan vendor:publish --tag=replicator-transfer-config

This creates config/replicator-transfer.php:

return [
    'handles' => [
        'page_builder',
    ],
];

Usage

Exporting

1. Open an entry that contains a configured replicator field in the Control Panel.
2. Click the action menu on the replicator field.
3. Select Export replicator.
4. An export.json file is downloaded to your machine.

Importing

1. Open the entry you want to import into in the Control Panel.
2. Click the action menu on the replicator field.
3. Select Import replicator.
4. Upload the export.json file in the confirmation dialog.
5. The imported sets are appended to the existing replicator content.

Development

Node.js 22+ is required to build the Control Panel assets:

npm install
npm run build

For hot reloading during development, run npm run dev in a separate terminal.

Quality

composer quality

This runs code style checks, static analysis, and the test suite.

Credits

• Bob Wezelman
• All Contributors

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

License

The MIT License (MIT). Please see License File for more information.