Migrate from Optimiser CRM to Freshsales

Optimiser CRM Contacts with standard fields (name, email, phone, address) map directly to Freshsales Contact. Email address serves as the dedupe key during import. Custom fields identified during scoping are recreated as typed Freshsales custom fields before import. Owner assignment resolves by matching Optimiser owner email to a Freshsales User record created during the user provisioning phase. Fields with zero data across all records are excluded to avoid creating dead columns in Freshsales.

Optimiser CRM Company records map to Freshsales Account. The company name becomes the Account Name field and is used as the dedupe key. If the source export includes a domain field, it populates the Account Website field. Account records must import before Contact records so that the Account-Contact relationship resolves at insert time. Where an Optimiser Company has no associated Contacts, it still migrates as a standalone Account.

Optimiser CRM Deals carry stage, deal value, expected close date, and owner assignment. The pipeline stage names are configurable per Optimiser instance, so we extract the full stage list during scoping and apply a stage-mapping table to Freshsales' default Deal pipeline stages (Appointment Scheduled, Qualified to Buy, Presentation Scheduled, Decision Maker Bought-In, Contract Sent, Closed Won, Closed Lost). Deal owner resolves via the User email mapping. Custom properties on Deals migrate as Freshsales custom fields created before Deal import.

Optimiser Lead records include status, source, and score fields. On Freshsales Growth, Pro, or Enterprise, Leads migrate as a separate Lead module record. On the Freshsales Free plan, which lacks a standalone Lead module, Leads are converted to Contacts during migration and the original Lead status is preserved in a custom field. We confirm the destination Freshsales edition before deciding which path applies. Duplicate email addresses across Leads and Contacts on the destination receive a reconciliation note rather than causing import failure.

Calls, emails, meetings, and notes logged against Contacts or Deals in Optimiser export as activity records. We import these in chronological order by setting the activity timestamp from the source. Calls map to Freshsales Activity with the call duration and disposition preserved in custom fields. Emails, meetings, and notes map to the corresponding Freshsales Activity types. All activities associate to the correct parent Contact, Account, or Deal via the lookup reference resolved at migration time. If the destination is Freshsales Free, note and meeting types are supported but call logging may require a manual custom field approach.

Every custom field on Contacts, Companies, and Deals requires individual review during scoping because Optimiser instances carry their own schema. We request a trial export or field inventory from the customer to enumerate all active fields before migration. Each field is recreated in Freshsales with a matching type (text, number, date, dropdown, multi-select, checkbox) before any data import begins. Fields with zero data across all records are excluded. The total custom field count directly affects migration pricing and timeline because each field is a separate configuration step.

Optimiser CRM user records carry name, email, and role. We map Optimiser users to Freshsales users by email address. The customer's admin provisions Freshsales user accounts before the migration run begins. Any Optimiser owner without a matching Freshsales user goes into a reconciliation queue for the admin to resolve before record import resumes, because OwnerId is a required reference on Deals and Activities.

Tags applied to Contacts or Deals in Optimiser export as label values. Freshsales supports labels on Contacts, Accounts, and Deals as a native feature. We migrate tags as-is and create matching label sets in Freshsales during the schema configuration phase. If the destination is Freshsales Suite (the AI-powered tier), tags can also be used as Freddy AI segmentation inputs, which is a value-add compared to Optimiser's static tagging.

Optimiser CRM allows configurable pipeline stages per deal type. Each Optimiser pipeline migrates to a Freshsales pipeline on Growth and above; Free tier is limited to a single default pipeline. We extract the full stage list and map each Optimiser stage name to the corresponding Freshsales stage value. Stages with zero records in Optimiser are flagged but omitted from the destination to keep the pipeline clean.

Workflows, assignment rules, and triggered sequences built in Optimiser CRM are stored in the platform's proprietary logic layer and are not accessible via export. We do not migrate automations as code. We deliver a written inventory of every active automation the customer identifies during scoping, mapped to Freshsales' equivalent workflow builder feature. This document is handed off to the customer's admin for manual rebuild post-migration.