Migrator For Elementor Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Migrator for Elementor copies hand-picked Elementor content from one of your WordPress sites (for
example a staging site) to another one of your sites (for example production). The same plugin is
installed on both sites.
The destination PULLS. The source only makes pages available; the destination’s administrator
lists them on the destination, approves them, and only then does the destination read and import
them. Nothing is pushed to the destination and nothing is stored there before that approval.
Each page is imported with everything it needs: its media, the Elementor templates it uses (nested
templates included), the global colors and fonts it relies on, its parent page, and the IDs it
references are rewritten to the matching objects of the destination.
How it works
- On the SOURCE site open Migrator for Elementor, choose Source site and click
Generate connection key. - On the DESTINATION site open Migrator for Elementor, choose Destination site, enter the
source URL and the key on Source & options, Save, then Test Connection. - On the source Pages tab (or Templates tab) select items and click Send to destination
(or Send on one row). They are only made available: the Sent to destination tab lists
them, and you can withdraw them. - On the destination, the administrator opens Incoming changes. The list is read live from the
source. They select items and click Approve and import selected (or Reject selected). - The destination then imports the approved items (and the templates, media, Site Settings and
parent pages they need), with overall and per-item progress, Pause, Resume, Cancel, Retry and
Retry Media. Progress is saved after every step. The source’s Sent to destination tab shows
each item as imported, failed or rejected. - Optional: tick Auto Sync on a page or template on the source. Saving it in Elementor makes it
available again; it is still imported only when the destination’s administrator approves it.
Approval and security
- The source never sends anything on its own and cannot change the destination. It answers signed,
read-only requests from the destination, and only for the items its administrator made
available (plus the templates, media, Site Settings and parent pages they use). - The destination stores nothing from the source before its administrator approves. The import
then runs in that administrator’s own session (wp-admin, nonce, manage_options). - No request is ever run as a user of the other site, and the connection key cannot be used to
log in. Requests are signed with HMAC-SHA256 and a single-use nonce, valid 5 minutes, and the
key is bound to one destination.
What is imported
- Page / post fields: title, slug, content, excerpt, status, password, parent page (an Elementor
parent missing on the destination is imported first), author (matched by login / e-mail),
dates, menu order, page template, featured image, terms (missing terms are created). - All Elementor data and meta. Elementor meta removed on the source is removed on the destination.
- Theme / SEO / ACF post meta, per the source’s options: Astra, OceanWP, GeneratePress, Kadence,
Yoast, Rank Math, ACF values, plus custom keys. - References by ID, rewritten to the destination objects: templates (shortcode, Template / Loop
widgets, global widgets, popups), posts and products (query controls, dynamic tags, ?page_id=
links, Contact Form 7 / WPForms / WooCommerce shortcodes), terms, users, menus, media (galleries,
Elementor 4 image controls, ACF image fields), Theme Builder and popup display conditions.
A referenced object missing on the destination is reported and the reference is cleared, never
left pointing to another object. - Media: absolute, relative and CDN upload URLs. Files are deduplicated (also files uploaded by hand
on both sites); a file replaced on the source is imported again; large files are read in parts. - Elementor templates of every type, the Site Settings (global colors and fonts are added
automatically when a page needs them), Elementor Pro custom fonts and custom code, and every
post type edited with Elementor.
Before an item is imported, the destination checks: Elementor version, Flexbox Containers / Nested
Elements features, widgets (Elementor Pro and add-ons), page template, ACF fields, shortcodes.
Blocking problems stop the item (option), the others are listed as warnings.
Two import modes (destination, Source & options):
- Best effort (default): every approved item is imported as completely as possible. The page on
the destination is overwritten (also one with the same slug that this plugin did not create),
files the destination refuses or that cannot be read are skipped, a template that fails does not
block the page, and every problem is listed as a warning. - Restricted: choose the situations that stop an item (nothing is written): same slug not created
by the plugin, local copy edited, refused file type, media not imported, failed template / Site
Settings / parent page, missing Elementor widgets / features / version.
Deletions are never offered automatically: on the source, a page in the trash can be offered as a
“move to trash” request, which the destination’s administrator approves like any other change.
Pages moved to a new path get a 301 redirect on the destination.
Trademarks
Elementor is a trademark of Elementor Ltd. This plugin is an independent project; it is not
affiliated with, endorsed by or sponsored by Elementor Ltd.
External services
This plugin does not use any third-party service, does not track users and sends no data to the
plugin author.
It only connects two WordPress sites that you own and configure yourself, both running this
plugin: the destination reads from the “Source URL” entered on its Source & options tab, with the
connection key generated on that source.
- What is transferred, and when: only when the destination’s administrator opens Incoming changes
(the list of items made available) and approves items (their content and settings, the media files
they use, the post meta chosen in the source’s options), plus the result reported back to the
source (imported / failed / rejected, the destination’s URLs of the imported page). - How: signed HTTPS requests from the destination to the source (HMAC-SHA256 with the connection
key, single-use nonce). The connection key itself is never transmitted. - Who receives it: only your own destination site. Its terms and privacy policy are your own.
Nothing is transferred until both sites are configured and the destination’s administrator acts.
Privacy
On the source site the plugin stores the connection key (and the destination bound to it), its
options, the list of items made available with the destination’s answers, and the last import date
of each page. On the destination site it stores the source URL and connection key, its options, the
progress of an approved import and, on each imported post or media, the identifier of its source
(used to update it instead of duplicating it). It does not collect personal data. Page content may
contain personal data you entered yourself; it is copied to your own destination site only.
Limitations
- Content without Elementor (WooCommerce products, posts not built with Elementor, ACF field groups,
Gravity Forms forms) is not imported: references to it are matched by slug, so it must exist on the destination. - Elementor Pro custom icon sets are not imported.
- The source must be reachable from the destination (a staging site behind a login wall or HTTP
authentication must let the destination’s requests through). - An approved import continues in the background through WP-Cron when the screen is closed.
Screenshots
No screenshots provided

