Migrate from OpenCRM to Freshsales

OpenCRM Company records map directly to Freshsales Account records. We use the Company name as the primary matching key during upsert, creating an Account in Freshsales for every OpenCRM Company. Account is the first object imported because Contacts in Freshsales carry an AccountId link that must be satisfied at insert time. Any OpenCRM Company that references a non-existent or deleted owner is flagged for owner reconciliation before import.

OpenCRM Contact records map to Freshsales Contact. Each Contact is linked to the corresponding Freshsales Account via AccountId resolved from the OpenCRM Company-to-Contact relationship. Email address is used as the dedupe key. OpenCRM's firstname and lastname split into Freshsales first_name and last_name; any single-name OpenCRM records are handled with a firstname/lastname normalisation rule during transformation. Owner assignment resolves by email match to Freshsales User.

OpenCRM Deals map to Freshsales Deal records. The OpenCRM dealstage property maps to Freshsales deal_stage using a stage-mapping table produced during scoping and confirmed by the customer. Deal value, expected close date, owner, and any linked Contact or Company references migrate directly. Closed-Lost and Closed-Won statuses from OpenCRM map to the equivalent Freshsales stage values in the mapping table.

OpenCRM allows fully custom pipeline stage names per workflow. These rarely align 1:1 with Freshsales deal stages. We produce a stage-mapping table during scoping that maps each OpenCRM stage name to the corresponding Freshsales stage label, with a probability value for each stage. The customer approves the table before we run the Deal import, and we apply the mapping during the transform step.

OpenCRM activity records (calls, meetings, tasks) stored with date/time formats and owner fields migrate to Freshsales Activity records. We normalise timestamps to UTC before loading. Owner names are resolved to Freshsales User IDs via the User mapping. Call disposition and duration from OpenCRM map to Freshsales custom activity fields if configured, otherwise to the default activity notes field.

OpenCRM Notes attached to contacts, companies, or deals require parent-entity mapping to preserve the correct association in Freshsales. We link Notes to the corresponding Contact or Account using the relationship information from OpenCRM. Note body migrates as plain text. We run a post-import audit comparing note-parent linkage counts between source and destination to confirm no orphaned Notes were created during the migration.

OpenCRM custom fields on Companies, Contacts, and Deals require field-by-field discovery during scoping. We map each custom field to a Freshsales custom field of the equivalent data type (text, number, date, dropdown, checkbox). Multi-select picklists in OpenCRM map to Freshsales multi-select fields. Any OpenCRM custom field without a direct Freshsales equivalent is escalated to the customer for schema decision before import.

OpenCRM Owner records referenced on Contacts, Companies, and Deals are resolved by email match against Freshsales User accounts. Any OpenCRM Owner without a matching Freshsales User goes into a reconciliation queue, and we flag this to the customer's admin for provisioning before the record import phase begins. OwnerId references on Deals and Contacts must resolve successfully for migration to proceed past the data-load phase.

OpenCRM tag-based categorisation on Contacts and Companies migrates to Freshsales Labels. Tags stored as comma-separated strings in OpenCRM custom fields are split into Freshsales Label assignments during the transform step. The customer chooses whether Labels should be attached to Contacts or Accounts during scoping.