Import, Migration & Rollback

Inspect competitor data before writing and keep a short-term path back

Supported Sources

Migration is field-mapped rather than a raw database copy. Preview shows what the selected source importer can translate before anything is written.

Source	Imported fields	Important limitation
Yoast SEO	Post and term SEO meta; title, social, sitemap, and site-schema settings; redirects; Local SEO locations	Redirects require Yoast’s Premium redirect table. Only mapped meta, schema, and location fields are migrated.
All in One SEO (AIOSEO)	AIOSEO 4 and legacy post meta; term meta; title, social, sitemap, and site-schema settings; redirects	Location data is not imported. Redirects require the AIOSEO Pro redirects table.
Rank Math	Post and term SEO meta; mapped per-post schema; title, social, sitemap, and verification settings; redirects; Local SEO locations	Unsupported schema types, fields, templates, and redirect comparisons are skipped or normalised to supported ProRank shapes.
SEOPress	Post and term SEO meta; title, social, sitemap, supported advanced and local-schema settings; enabled published redirects	The current Migration Center does not import SEOPress location records as a separate location data type.
Redirection	Redirect source, target, status code, regex flag, and enabled state	Only URL/redirect action types with a usable target are imported; other actions are skipped.
Schema Pro	Supported fields from published schema templates, applied to published posts selected by known display rules	Unknown display selectors, excluded targets, unsupported schema types, and incomplete mappings are skipped.
All in One Schema Rich Snippets	Per-post Article, Event, Person, Product, Recipe, Service, SoftwareApplication, and VideoObject fields	Only recognised legacy type IDs and mapped fields are imported; unsupported or incomplete records are skipped.

“SEO meta” covers the supported title, description, focus-keyword, canonical, robots, social, image, primary-category, and breadcrumb fields available in that source—not every private field the source plugin stores. The badges beside a source show the data types included; the current screen does not provide separate per-type checkboxes.

Preview a Migration

Open ProRank SEO → Import/Export.
Select a detected source and review the data-type badges shown for it.
Choose Preview Import and review the discovered counts and skipped records.
Apply only when the preview matches the source data you intend to move.

Preview performs the same bounded discovery as the real migration but does not change posts, terms, options, redirects, or schema data.

Undo a Completed Import

A successful competitor import creates an Undo Import action for seven days. ProRank restores the values recorded immediately before that import. If a multi-source import fails, completed sources are rolled back in reverse order.

The rollback journal is a migration safeguard, not a full backup. Take a database backup before a large production migration and do not rely on rollback after the seven-day retention window.

Move ProRank Settings Between Sites

The same workspace exports and imports ProRank settings, module states, redirects, and supported SEO metadata as a JSON file. This file workflow is separate from competitor migration and replaces the selected destination settings when imported.