Elementor Export/Import Templates vs PostDeploy: a design vs a live page
You need to move an Elementor page to another site, and right there in the Templates menu is an "Export Template" button. It feels like exactly the right tool — it's Elementor's own feature, built by the people who built the page builder. Export a .json file on one site, import it on the other, done. Except that's not quite what it's for, and the gap between what it actually does and what "move this page" means is where people get stuck.
What Export/Import Templates is actually for
Elementor's Template Library (Templates → Saved Templates, or the broader Template Kits feature in newer versions) is built around templates — reusable designs: a header, a hero section, a landing page layout, a whole starter-site kit. "Export Template" saves the Elementor design data for one of these as a portable file. "Import Templates" reads that file back in on another site and adds it to that site's own Template Library, ready to be applied to a page.
That's a real, useful feature — handing a design to a client, reusing a section across projects, moving a Template Kit's starter content to a new site build. It's also the official way to move a Loop Grid's Loop Item template between sites when you're not pushing the underlying page through anything else.
What's in the file, and what isn't
An exported template captures the Elementor widget tree — the actual design. What it doesn't capture is the thing that makes a published page a page: its post status, its slug and URL, its categories and tags, its featured image as post meta, any ACF or other plugin data attached to it, its position in your site's actual content. Importing a template creates a new template in your library — you still have to turn that into an actual page, assign it the content, and wire up everything the design doesn't carry.
That's fine when the point was always the design, not a specific already-published page. It stops being fine the moment you're trying to answer "can I get this exact page, as it exists on staging right now, onto production" — because that's not a template-export problem, it's a move-a-post problem, and Elementor's own export tool was never built to solve that one.
Where this is genuinely the right tool
- Handing a reusable section or page design to someone else, or between your own projects.
- Starting a new site from a Template Kit instead of from scratch.
- Moving a Loop Item template that a Loop Grid widget references, as its own standalone step.
- Backing up a design you built, independent of any one page it's currently assigned to.
Where it falls short of moving a live page
- No live content comes with it. Categories, tags, custom fields, the featured image as real post data — none of it is part of a template export.
- It creates something new, not updates something existing. Importing doesn't know about the page it's "supposed" to update on the destination — there's no concept of "this is the same page, already pushed once before."
- No conflict detection. Nothing checks whether the destination page changed since your last export, so there's no warning before you overwrite someone else's edit.
- No undo. If the import goes wrong, there's no built-in snapshot of what was there before.
- One page, one export, every time. Moving ten finished pages means ten manual export/import round-trips, not a bulk operation.
What PostDeploy does differently
PostDeploy pushes the actual post — the real page, with its status, slug, taxonomies, and (Pro) its Elementor design, ACF fields, and WPML translation links resolved to what they should be on the destination, not copied verbatim from the source. Push a page that was already sent there before, and it updates the existing page instead of creating a duplicate. Pro adds conflict detection (warns if the destination changed since your last push) and a snapshot before every overwrite, so a bad push has an undo. None of that is what Elementor's Export/Import was built to do — it's solving a genuinely different problem, and that's fine; they're not competing tools, they're the right tool for two different jobs.
Try it
PostDeploy Free moves Posts, Pages, and custom post types as plain content. PostDeploy Pro adds the Elementor, ACF, and WPML reference resolution described here, along with Rollback and bulk/scheduled deployment. See the side-by-side comparison page for a quick reference.