Move Content Between Environments

The $99 one-time fee gives you a single-site license for Transport, including every feature: portable .zip packages, UID-based reference resolution, automatic dependency ordering, field-level diff and selective merge, asset file transfer, multi-site support, queue-backed exports and imports with completion emails, detailed run reports, snapshot-based rollback, the full CLI, and all built-in plugin integrations. You also get one year of updates.

After the first year you can renew for $79/year to keep receiving updates and new features. If you choose not to renew, your installed version keeps working — you just won’t get updates.

No. Transport moves content, not schema. Sections, fields, entry types, volumes, and global sets are managed by Craft’s Project Config. Deploy your Project Config first, then use Transport for the content. Its pre-flight validation checks that the required schema already exists in the target before importing.

Every reference — relations, authors, structure parents, Matrix and Hyper links — is stored as a UID rather than a numeric ID. On import, Transport resolves each UID to the matching element’s local ID in the target site. That’s why content keeps working even when the same entry has a different ID on each site.

Transport works with any self-contained field out of the box, plus dedicated, tested handlers for Craft core element types, Matrix, relations, asset files, Verbb Hyper, FreeLink, FreeNav, Craft Commerce 5, Google Maps, SEOMatic, Verbb Navigation, Formie, and Solspace Calendar — with experimental handlers for Neo and Super Table. Handlers load only when the host plugin is installed. See the integrations guide for the full list and status of each.

Yes. Every import is snapshotted before it runs. From Transport → History you can roll back a completed import with one click — updated elements return to their prior state and elements the import created are deleted. Rollbacks are themselves snapshot-protected, so they can be undone too.

Yes. Transport has a full CLI for exports, imports (including dry runs), history, and rollbacks — ideal for CI pipelines and scheduled deployments. Anything the control panel can do, the CLI can do.

Products and variants are supported and tested — product type, SKU, base price, dimensions, tax and shipping categories, and custom fields. Orders, inventory levels, and catalog pricing are intentionally excluded — that data is environment-specific and shouldn’t be copied between sites.

No. Control panel exports and imports run as queue jobs rather than in the request, so the size of your content set isn’t a constraint — queue it, leave the page, and pick up the finished package or report in Transport → History. Tick “email me when it finishes” and it comes to your inbox instead. Console runs are synchronous by design, streaming live progress to the terminal so you can watch a deployment work.

Transport updates it rather than adding a second copy. Content routinely exists on two sites with unrelated UIDs — a single created independently on each, or content that predates Transport — so when a package element’s UID isn’t found, Transport matches the element that already exists by its natural key: a single’s section, a slug within its section or group, an asset’s filename in its folder, a user’s email. Matched elements are flagged in the import wizard before you run, and you can switch the behavior off for strict UID-only identity.

A detailed report of every element — added, updated, skipped, or failed — with the reason behind each skip and failure, a breakdown per element type, and how long it took. It’s stored with the run in Transport → History, printed at the end of every CLI run, and emailed to whoever started a queued run.

Transport requires Craft CMS 5.3 or later, PHP 8.2 or later, and the PHP ext-zip extension. It supports both MySQL and PostgreSQL databases.