Migrate from FIVE CRM to Freshsales

FIVE CRM Contacts map directly to Freshsales Contacts with standard field mapping for email, phone, mobile, address, and owner assignment. The Freshsales Contact object uses First Name and Last Name separately; FIVE CRM contacts with a single-name display name require a name-split transform during import. We preserve any contact-level custom fields and map them via the pre-migration field mapping session.

FIVE CRM Lead records merge into Freshsales Contact because Freshsales does not maintain a separate Lead object. The original FIVE CRM lead_source field maps to Freshsales Lead Source on Contact, and any qualification status from FIVE CRM maps to Freshsales Contact Status. The merge rule is applied at migration time based on the customer's current Lead use: if Leads represent warm prospects not yet contacted, they enter Freshsales as Contacts with an initial status of New; if they represent disqualified records, they enter with a status of Lost.

FIVE CRM Companies map to Freshsales Accounts. We import Accounts before Contacts to satisfy the parent relationship. The FIVE CRM company domain maps to the Account Website field, and account_name maps directly. If FIVE CRM uses a custom industry or size field, we map it to the Freshsales Industry and Number of Employees fields during the field mapping session.

FIVE CRM Pipelines and their custom stage labels require explicit remapping to Freshsales Deal stages. During scoping, we enumerate every FIVE CRM pipeline and stage in use, compare them to the customer's intended Freshsales workflow stages, and produce a stage mapping table. Custom stage labels that have no Freshsales equivalent are renamed at migration time. Closed-won and closed-lost stage dispositions migrate as Freshsales Deal statuses.

FIVE CRM Deals map to Freshsales Deals with the pipeline stage remapped per the stage mapping table agreed in scoping. Deal amount, expected close date, owner assignment, and associated company and contact links transfer directly. FIVE CRM custom fields on Deals (such as deal type, product line, or renewal flag) map via the explicit field mapping session. If FIVE CRM uses multiple pipelines, each becomes a separate Freshsales Deal workflow filter.

FIVE CRM Campaigns track email marketing sequences and membership. Freshsales does not have a native Campaign object equivalent; we migrate campaign membership as a custom multi-select picklist or tag on the Contact record, preserving which campaigns each contact was a member of. Individual email engagement events (opens, clicks, replies) require a separate field mapping because Freshsales does not store per-event engagement logs in the same structure. We flag this limitation and recommend a campaign engagement summary export for admin review.

FIVE CRM Tasks map to Freshsales Tasks with due date, assignee, priority, and completion status preserved. FIVE CRM task types (call, email, meeting, follow-up) may need consolidation if the task type taxonomy differs from Freshsales' built-in task types. We map each FIVE CRM task type to the closest Freshsales task type during field mapping.

FIVE CRM uses custom fields extensively to support telemarketing-specific data capture. These fields are not consistently named or typed across tenants, and FIVE CRM does not expose a complete schema document via its public API. Every migration from FIVE CRM requires a pre-migration field mapping session during which we enumerate every active custom field, confirm its data type, and agree on a Freshsales destination. FIVE CRM's opaque error messaging makes it impossible to diagnose field type mismatches from the UI, so we validate all field types against the known FIVE CRM export schema before import. Skipping this step leads to silent type coercion or dropped values in Freshsales.

FIVE CRM Tags label records for segmentation and campaign targeting. Tags map to Freshsales Tags on the Contact or Account record. Multi-select tag fields may split into multiple rows during import if Freshsales stores them as separate tag entries rather than a delimited field; we normalize this during the transform step.

File attachments associated with Contacts, Companies, or Deals migrate via file reference re-upload or direct attachment import depending on the target Freshsales configuration. Attachments over 10MB require separate handling due to API upload size limits. We flag large attachments during scoping and handle them in a separate file migration pass.