Migrate from Cirrus CRM to Freshsales

Cirrus CRM Contact records map to Freshsales Contact with direct field mapping on name, email, phone, address, and owner. Custom fields on Contacts migrate after we validate field types (text, number, date, picklist) against Freshsales Growth plan field limits (35 custom fields total across all objects). Any Cirrus CRM Contact with a relationship to a Company maps the relationship via Freshsales Contact's linked_account_id. We use email as the dedupe key during import to prevent duplicate Contacts.

Cirrus CRM Company records map to Freshsales Account. Cirrus CRM's built-in geographic enrichment (latitude/longitude from its maps feature) migrates to Freshsales Account custom fields if the destination plan supports geo fields; otherwise we map to a text address composite field. Credit information stored in Cirrus CRM Companies migrates as a custom currency or text field on Account with a note that the customer should verify relevance in Freshsales context. Account is created before Contact import to satisfy the linked_account_id lookup.

Cirrus CRM Deal records map to Freshsales Deal with deal name, amount, expected close date, owner, and stage name preserved. The Deal-to-Contact and Deal-to-Company lookups resolve by matching email and company domain respectively at migration time. Cirrus CRM deal stage labels migrate as Freshsales Deal Stage values; we ask the customer to confirm the target Freshsales pipeline stage mapping before migration because stage probability and win/loss criteria differ between systems.

Cirrus CRM pipeline definitions (stage order, stage labels, automation triggers) require configuration in Freshsales. Stage labels from Cirrus CRM map to Freshsales Deal Stage values; stage probability percentages map to Freshsales stage-level probability. We document the pipeline configuration in the migration runbook and the customer configures the Freshsales pipeline via admin settings before deal records import begins. ERP-linked stage automation triggers do not migrate and are listed for manual rebuild.

Cirrus CRM Quotes map to Freshsales Quotes with line item detail. Quote-to-Deal linkage is preserved by resolving the parent Deal in Freshsales before Quote import. We confirm with the customer whether Quotes should land as Freshsales native Quotes with line items or as formatted text notes if the line-item object approach exceeds their plan capability. Cirrus CRM Quote status (draft, sent, accepted, lost) maps to Freshsales Quote Status field.

Cirrus CRM Orders are generated from Quotes and carry ERP-linked invoice associations. We ask the customer whether Orders should map to Freshsales Deals with order-specific custom fields (order number, order date, ERP invoice reference) or to Products and Deals with line-item detail. Order-to-Quote linkage is preserved by matching Quote ID or Quote number during migration. If the ERP sync layer was the source of truth for order data, we flag records that may be stale due to sync offline periods and present a remediation option before import.

Cirrus CRM Activity records (calls, emails, tasks) migrate to Freshsales Activity with timestamp, owner, and linked Contact or Deal preserved. Activity type maps from Cirrus CRM's activity classification to Freshsales Activity Type field. Freshsales stores activities as timeline entries per Contact or Deal; we use the parent record lookup (contact_id, deal_id) to associate each activity at migration time. Call duration and disposition from Cirrus CRM migrate as custom fields on the Freshsales Activity record.

Cirrus CRM Campaigns track objectives and campaign-level metrics. We migrate campaign name, status (active, completed, archived), and owner to Freshsales Campaign. Individual campaign member associations (which Contacts were added to which Campaigns) migrate to Freshsales Campaign Member records linked by Contact email match. We confirm campaign member scope with the customer before migration because large campaign member lists can extend migration time.

Cirrus CRM tenant-specific custom fields on Contacts, Companies, and Deals migrate to Freshsales custom fields after field-by-field type validation. We ask the customer to provide a field configuration screenshot or export before scoping, then validate field types (text, number, date, picklist) in a test batch of 50 records before the full dataset. Freshsales Growth plan caps custom fields at 35 total; Pro at 50; Enterprise at 100. We check total custom field count against the target plan before migration and flag any overflow for customer decision on plan upgrade or field consolidation.