Migrate from Brevo Marketing Platform to Freshsales

Discovery and account tier audit

We audit the source Brevo account across plan tier (Free, Starter, Standard, Professional, Enterprise), custom object presence, pipeline count, active automation workflows, tag and segment definitions, contact volume, and engagement history size. We pair this with a Freshsales plan recommendation (Sprout free tier through Forest $89/user/mo) based on the customer's pipeline complexity and custom object needs. The discovery output is a written migration scope document listing every object in scope, any excluded due to plan constraints, and the estimated row counts per entity.

Export method confirmation and extraction

We confirm the available export path for Brevo based on account tier: Enterprise accounts use the Customer Data Platform export; all others use the Contacts API with pagination and one-off CSV exports from the UI. We extract Contacts, Companies, Deals, pipeline and stage configurations, tags, segment definitions, custom object records (if applicable), and owner records. Engagement history (email opens, clicks, campaign sends) is extracted as statistical summaries rather than individual event records because Freshsales does not replicate Brevo's campaign engagement timeline.

Schema design and Freshsales field mapping

We design the destination schema in Freshsales before any data moves. This includes mapping Brevo Companies to Freshsales Organizations with address and industry fields, Brevo Deals to Freshsales Deals with pipeline and stage assignments preserved, and any Brevo custom properties to Freshsales custom fields or contact traits. Custom objects (if supported on the destination plan) are created in Freshsales with matching field types and lookup relationships. The schema design is validated in a Freshsales trial or sandbox environment before production migration begins.

Owner reconciliation and User provisioning

We extract every distinct Brevo Owner referenced on Contacts, Companies, and Deals and match by email against the Freshsales User table. Owners without a matching Freshsales User are held in a reconciliation queue. The customer's admin provisions any missing Users (active or inactive depending on whether the original Brevo user is still employed). Migration cannot proceed past Contact and Deal import because owner assignments require a valid Freshsales User reference.

Production migration in dependency order

We run production migration in record-dependency order: Users (manual provisioning confirmed), Organizations (from Brevo Companies), Contacts (with Organization lookup resolved), Deals (with Contact, Organization, and Owner lookups resolved), Tags and segment memberships (applied to Contacts by email match), Custom Objects (with lookups to Contacts and Organizations resolved). Each phase emits a row-count reconciliation report before the next phase begins. Any records that fail import due to field validation or lookup misses are routed to an exception queue for manual review.

Cutover, validation, and automation rebuild handoff

We freeze Brevo write access during cutover, run a final delta migration of any records modified during the migration window, then enable Freshsales as the system of record. We deliver the automation workflow inventory document to the customer's admin team for rebuild in Freshsales or a connected marketing tool. We support a three-day hypercare window where we resolve any reconciliation issues raised by the customer's sales team. We do not rebuild Brevo automation workflows as Freshsales sequences inside the migration scope; that is a separate engagement or an internal admin task.