Start a Project ↗

orravo.com / migrate

FluentCRM → OMailer

Move your subscribers, lists, tags, and automations from FluentCRM to OMailer with no email-history loss. Roughly 30 minutes for typical lists; longer for very large databases.

⏱ ~30 minutes (subscribers under 50k)● Low risk↗ Compare FluentCRM vs OMailer

Read this first

Both plugins keep all data inside your WordPress database. Subscriber records and history move via CSV; in-flight automations should be paused on the source, then re-created on OMailer with the same trigger conditions.

The migration, step by step

  1. 1

    Pause active campaigns + automations in FluentCRM

    2 min
    Go to FluentCRM → Campaigns → pause anything currently sending. Same in Automations. This stops new emails going out under the old plugin while you migrate.
  2. 2

    Export contacts from FluentCRM

    5 min
    FluentCRM → Contacts → Bulk Actions → Export. Pick "All" and "All fields including custom". You'll get a CSV with email, name, lists, tags, and custom-field values.
  3. 3

    Install OMailer + activate license

    3 min
    Upload the OMailer zip via Plugins → Add New → Upload Plugin. Activate, then paste your license key in OMailer → Settings → License.
  4. 4

    Recreate lists + tags in OMailer

    5 min
    OMailer → Lists → New List for each FluentCRM list. Same for Tags. Use identical names so the import maps cleanly.
  5. 5

    Import the FluentCRM CSV

    5–15 min
    OMailer → Subscribers → Import CSV. Upload the file, map columns to OMailer fields, set the import to assign matching list/tag names. The importer dedupes on email, so re-running is safe.
    # Or via WP-CLI for very large lists:
wp omailer subscriber import contacts-from-fluentcrm.csv --tag-from-column=tags --list-from-column=lists
  6. 6

    Recreate top automations

    10–20 min · per automation
    OMailer → Automations → New. Use the same trigger conditions as your FluentCRM automations (welcome series, abandoned-cart, etc.). OMailer's automation builder uses the same step types, so a side-by-side window works well here.
  7. 7

    Send a test campaign to yourself

    2 min
    OMailer → Campaigns → New → pick a small list (or use the "Test send" option) and verify the email lands and tracking pixels register.
  8. 8

    Disable + uninstall FluentCRM

    1 min
    Once your test send is clean, deactivate FluentCRM. Keep it installed for a week as a safety net before deleting — that way you can roll back if anything looks off in the first batch sent through OMailer.

Watch out for

Custom fields with the same key

If you used custom fields in FluentCRM, recreate them in OMailer with the same internal key BEFORE running the CSV import. The importer skips columns that don't map to a known field.

Bounced contacts

FluentCRM marks bounced/complained contacts internally. The CSV export includes the status column — OMailer respects it on import, so previously suppressed addresses stay suppressed.

Open / click history

Engagement history (opens, clicks, dates) doesn't cross over with the CSV — it stays in FluentCRM. If history is critical, keep FluentCRM installed (deactivated) for as long as you need to query it.

Try before you migrate

14 days of OMailer, no card.

Spin up OMaileron a staging site or a single page first. Move data only when you’ve confirmed it works for you.

Try free · 14 days · no card

OMailer details →

Checkout is briefly offline while we migrate processors.

Stuck mid-migration? Reply to hello@orravo.com — we’ll walk through it with you.