Yipresser Migrator for Admin Optimizer

By yipresser

0+ active installationsVersion 1.1.0

Migrate SEO settings, forms, and redirect rules into matching Admin Optimizer modules.

Description

Yipresser Migrator for Admin Optimizer is a companion plugin for Admin Optimizer. It helps site owners move data from supported third-party plugins into matching Admin Optimizer modules.

The migration workflow is built into the Admin Optimizer settings screen. Scan the site, review the available importers, choose migration options, and run the migration.

Supported sources:

  • Yoast SEO (SEO Manager)
  • All in One SEO (SEO Manager)
  • Rank Math (SEO Manager)
  • SEOPress (SEO Manager)
  • Contact Form 7 (Form Builder)
  • WPForms Lite and Pro (Form Builder)
  • Fluent Forms (Form Builder)
  • Redirection (Redirect Manager)

What can be migrated:

  • Site-wide title, description, schema, social image, and social profile settings where a matching Admin Optimizer SEO Manager field exists.
  • Per-post focus keyword, meta title, meta description, Facebook image, X/Twitter image, canonical URL, noindex value, and schema type where supported by the source plugin.
  • Public post types selected during migration. Posts and pages are selected by default.
  • Contact Form 7 forms, imported as Admin Optimizer Form Builder forms with their fields and mail settings mapped over.
  • WPForms forms, including supported fields and layout, the default enabled notification, and the default enabled confirmation. Adjusted and unsupported features are reported for review.
  • Fluent Forms forms, including supported fields and layout, one compatible primary notification with an optional matching autoresponder, the default confirmation, and compatible field conditions. Adjusted and unsupported features are reported for review.
  • Enabled plain URL rules from Redirection with safe internal targets and 301, 302, or 307 status codes. Existing Redirect Manager rules are never overwritten, and unsupported rules are reported for review.

Migration is read-only for source plugins. The tool reads supported source plugin options, post metadata, forms, and redirect rules, then writes mapped values into the matching Admin Optimizer module. It does not modify or delete source plugin data.

Migration is a one-time operation, not a sync: running (or re-running) an SEO importer writes mapped values over the destination SEO fields. Contact Form 7, WPForms, and Fluent Forms can skip previously imported forms. Redirection imports never overwrite an existing Redirect Manager rule.

For larger sites, per-post SEO migration runs in background batches through Action Scheduler. WPForms, Fluent Forms, and Redirection imports process bounded chunks while the migration screen polls for progress. Contact Form 7 import runs immediately.

SEO Manager, Form Builder, and Redirect Manager are Admin Optimizer destinations. The installed Admin Optimizer version must provide the matching destination storage contract. The destination module does not need to be enabled before migration.

Installation

  1. Upload the yipresser-migrator-for-admin-optimizer folder to the /wp-content/plugins/ directory, or install the plugin from the WordPress Plugins screen.
  2. Activate Yipresser Migrator for Admin Optimizer through the Plugins screen in WordPress.
  3. Make sure Admin Optimizer is active and provides the destination named for your migration.
  4. Go to the Admin Optimizer settings screen and open the Migration tab.
  5. Click Start Scanning, review the detected importers, choose the options you want, and start the migration.

FAQ

Does this plugin change my existing source plugin data?

No. Source plugin data is read only. The migration writes mapped values into the matching Admin Optimizer module and leaves source settings, post metadata, forms, entries, and redirect rules in place.

Which plugins are supported?

Yoast SEO, All in One SEO, Rank Math, and SEOPress migrate into SEO Manager. Contact Form 7, WPForms Lite/Pro, and Fluent Forms migrate into Form Builder. Redirection migrates compatible rules into Redirect Manager.

Can I skip existing Admin Optimizer data?

No, not for SEO settings or per-post SEO fields. Migration overwrites each mapped destination Admin Optimizer SEO Manager setting or post field with the corresponding value read from the source plugin — this is a one-time migration, not a two-way sync. Back up your site before running a migration if you’ve already configured Admin Optimizer SEO Manager and want to keep those values.

Contact Form 7, WPForms, and Fluent Forms imports include an option to skip previously imported forms. Redirection tracks imported source rules and also checks destination source paths, so re-running it does not create duplicates or overwrite conflicts.

Which post types are migrated?

For SEO importers, posts and pages are selected by default. The migration screen lets you choose from the public post types available on the site before running each importer. This option doesn’t apply to Contact Form 7, WPForms, or Fluent Forms, which migrate forms rather than posts.

Are all source plugin fields migrated exactly?

Only data with a matching Admin Optimizer destination is migrated. Some source features have no equivalent and are skipped. The migration screen includes mapping tables so you can review the supported scope before running it.

WPForms migration reports exact, adjusted, and unsupported fields. It imports the default enabled notification and confirmation where supported, reports additional or conditional configurations that cannot be represented, and does not migrate WPForms entries, payments, integrations, registrations, or post-submission behavior. Existing WPForms entries remain available in WPForms.

Fluent Forms migration reports exact, adjusted, and unsupported fields. Forms are imported as drafts unless you choose to publish them. One compatible, unconditional notification to a single address is imported, plus one matching autoresponder to an Email field. Other notifications, routing, CC/BCC, attachments, conditional notifications, and notifications that use unsupported tokens are reported and not imported. Compatible single-step field conditions are imported on every site but only run when Admin Optimizer Pro is active; rule sets that cannot be represented are left out in full. Fluent Forms entries, payments, calculations, multi-step forms, signatures, repeaters, CAPTCHA, time fields, integrations, and styling are not migrated. A form with no importable fields is skipped rather than created empty. Existing Fluent Forms entries and shortcodes remain unchanged in Fluent Forms.

Redirection migration supports enabled, non-regex URL matches with safe internal targets and 301, 302, or 307 status codes. Conditional or query-string matches, non-URL actions such as 410 errors, external targets, groups, logs, and statistics are not migrated. Unsupported rules and conflicts remain in migration history with their reason; exact duplicates are counted as existing rules.

How does the plugin handle large sites?

Per-post SEO migration runs in background batches using Action Scheduler. Contact Form 7 runs immediately. WPForms and Fluent Forms process up to 20 selected forms per request, and Redirection processes up to 100 rules per request; both continue through progress polling.

Should I back up my site first?

Yes. Source data is not changed, but migration writes data into Admin Optimizer. A fresh database backup is recommended, especially because re-running an SEO importer overwrites mapped SEO destination values.

Changelog

1.1.0

  • Added: Fluent Forms importer for Form Builder forms, with supported fields and layout, one compatible notification and autoresponder, the default confirmation, and compatible field conditions.
  • Added: Field conditions import on Free and Pro; they run only when Admin Optimizer Pro is active.
  • Added: Fluent Forms scan labels forms with nothing to import and skips them instead of creating empty drafts.
  • Added: Per-form compatibility reporting with exact, adjusted, and unsupported field counts.

1.0.6

  • Changed: CF7 and WPForms imports now use Form Builder’s canonical save and sanitization pipeline, including structural Submit Buttons and current Row child-width normalization.
  • Fixed: CF7 and WPForms Hidden fields now import as Form Builder Hidden fields with their configured values preserved.
  • Fixed: AI-generated forms now use the same canonical Form Builder save path.

1.0.5

  • Added: multiple keywords import from Yoast, SEOPress, RankMath and AIOSEO

1.0.4

  • Fixed: Removed commercial, license, tier, and module-activation restrictions from all migration execution paths.
  • Changed: Migration availability now uses neutral technical destination-compatibility checks for SEO Manager, Form Builder, and Redirect Manager.
  • Added: Informational destination-availability helper text on importer cards and after successful migrations.
  • Added: Human-readable JavaScript and CSS sources to the WordPress.org package, with source and build instructions.

1.0.3

  • Added: WPForms Lite and Pro importer for Form Builder forms, supported fields, notifications, and confirmations, with compatibility reporting and duplicate-import protection.
  • Added: Redirection importer for compatible internal URL rules, with bounded batches, duplicate protection, and retained skip reasons.

1.0.2

  • Added: CF7 importer
  • Fixed: Various SEO importers bugs.

1.0.1

  • Added: plugin updater

1.0.0

  • First release with yoast seo, aioseo, rankmath, seopress.