---
title: Migrate from FluentCRM
description: Move the lists, people, tags, fields, automations and sender settings you choose from FluentCRM into Hive Mail, check the plan first.
url: "https://hiveplugins.com/docs/hive-mail-migrate-from-fluentcrm/"
updated: "2026-10-28"
category: Hive Mail
---

# Migrate from FluentCRM

**Settings > Migration** moves the parts of FluentCRM you choose into Hive Mail, shows a plan before it changes anything, and keeps everyone who opted out opted out. FluentCRM itself is only read: nothing in it is changed, switched off or deleted.

The **Migration** tab appears only when Hive Mail finds FluentCRM data (the plugin can be active, or off with its data still in the database). Back up your site first. For a simple copy of contacts, or of another plugin, see [Move over from another plugin](/docs/hive-mail-move-from-another-plugin/).

## What it brings over

| FluentCRM | In Hive Mail |
| --- | --- |
| People in the lists you tick | Contacts (email, names, phone, country, created date, WordPress user link), same status with the rules below |
| The lists you tick; the tags those people have | Lists and tags with the same names (existing ones are reused) |
| Custom fields and address-type fields (city, state, postal code, date of birth and similar) | Custom fields |
| Automations you tick | Flows copied as drafts, with their emails as new templates |
| Sender name, sender email, reply-to email, business name, business address | The same settings in **Settings > General**, only the ones you tick |

**Not carried over** (the screen lists them with a count): campaigns and their reports, saved email templates, notes on contacts, smart links. People in none of the ticked lists are not brought over. Migrated contacts show the source "migration".

## Steps

1. Go to **Settings > Migration**. Wait for "Reading FluentCRM…". The blue box shows how many contacts and lists FluentCRM holds.
2. **1. Lists:** tick the lists to bring (**Tick all** / **Tick none**). Someone in two ticked lists is moved once and joins both. Until you tick one, the other cards stay hidden.
3. **2. People:** tick the statuses to bring: **Subscribed**, **Pending**, **Unsubscribed**, **Bounced**, **Cleaned (bounced)**, **Complained**. Decide on **These people agreed to receive my emails** (see below).
4. **3. Tags** and **4. Fields:** untick what you do not need.
5. **5. Automations:** tick the ones to copy. Ones running in FluentCRM and not yet copied are ticked for you; "already copied" ones are switched off. Read the orange warnings.
6. **6. Settings:** tick the settings to copy. A row is ticked for you only when Hive Mail's value is empty or still the starting value.
7. Press **Review what will happen**. **Check, then start** says "Nothing has been changed yet." This is the dry run: three numbers (people, new, already in Hive Mail), the lists, tags, fields, automations and settings, and up to 12 sample people. Change a tick and the plan clears; review again.
8. Press **Start the migration**. A bar shows "Moving people… 120 of 5,000".

![The Lists card with three lists ticked and badges for each list's statuses.](https://hiveplugins.com/wp-content/uploads/2026/10/hivemail-migration-lists-02.webp)

![The Check, then start card with the three numbers, the status table and the sample of people.](https://hiveplugins.com/wp-content/uploads/2026/10/hivemail-migration-review-07.webp)

You can leave the page. The migration continues through your site's scheduled tasks, so cron must work ([Scheduled sending and cron](/docs/hive-mail-scheduled-sending-and-cron/)). People move 200 at a time and the place is saved.

## Statuses and permission

| In FluentCRM | In Hive Mail |
| --- | --- |
| Subscribed | Subscribed if you tick the permission box; otherwise Pending, asked to confirm again |
| Pending | Pending |
| Unsubscribed | Unsubscribed, never emailed |
| Bounced, Cleaned | Bounced, never emailed |
| Complained | Complained, never emailed |

Tick **These people agreed to receive my emails** (off by default) only if that is true for everyone you bring. Your name and the time are saved as the record. See [Double opt-in](/docs/hive-mail-double-opt-in/). If you untick a kind of person who opted out, they are not brought in at all and could be emailed if they join again later; keeping them in, as opted out, is safer.

## Automations

Copied as drafts, they send nothing until you switch them on. Switch the FluentCRM automation off first, or people get both.

- **Copied:** the start "A contact joins a list", "A contact leaves a list", "A contact gets a tag" or "A contact loses a tag" (any other start becomes a manual start with a warning: choose a start before switching on); add or remove a tag or list; waits (a month = 30 days, over 365 is shortened to 365); emails to the contact, with FluentCRM merge tags changed to Hive Mail's and unknown ones removed; if/else steps on tags, lists, status or whether the person has ordered; and "end this automation".
- **Not copied:** steps that update a field, call a webhook or run a WordPress hook, and anything else Hive Mail does not know. Each is named in a warning.

## When it finishes

**Migration finished** shows **new contacts**, **already here, updated** (only blanks filled, joined the chosen lists and tags), **kept opted out, never emailed** and **left out**. Each automation shows **Copied as a draft**, **Was already copied** or **Could not be copied**, with **Open it**. The **Left out** table shows the first 10 with the reason; **Download the full list** gives every one (fluentcrm_id, email, status, problem). Common reasons: an invalid email, an address on the do-not-email list, a contact in the trash ("Restore it to update it").

## Safety

- **Opt-outs are always kept.** If the same email is already a Hive Mail contact who could be emailed, they are set to the opt-out too. Nobody is made "more subscribed". Bounced and complained addresses go on the do-not-email list.
- **Running it again is safe.** Lists, tags and fields are found by name, people already moved are not added twice, and copied automations are not copied again. If it stops, start it again and it carries on.
- Matching is by email. Existing contacts keep their details; only blanks are filled.

> **Warning:** There is no undo. To reverse a migration you must delete the contacts, lists, tags, fields, flows and templates it made, by hand. Deleted contacts stay in the trash for 30 days.

This is information, not legal advice.

Next: [Contact statuses](/docs/hive-mail-contact-statuses/), [Automation basics](/docs/hive-mail-automation-basics/), [Import errors and how to fix them](/docs/hive-mail-import-errors/).