Migrate from CentralStationCRM to Freshsales

CentralStationCRM stores all contacts as People regardless of qualification level. Freshsales maintains a separate Lead object for unqualified prospects and Contact for qualified records. We define a split rule during scoping (typically using any CentralStationCRM lifecycle or status property as the qualifier) and migrate qualified People to Freshsales Contact with an AccountId reference, and unqualified People to Freshsales Lead with a custom field preserving the original CentralStationCRM record ID. The customer's admin confirms the split logic before migration runs.

CentralStationCRM Company records map directly to Freshsales Account. The company name becomes the Account Name field. We create Account records first, then resolve the AccountId on each Contact record during import so that the Lookup relationship is satisfied at the moment of Contact insert. Company addresses (fetched via nested routes) map to Account address fields in Freshsales.

CentralStationCRM Deals map to Freshsales Deals 1:1 with stage, value, assignee, and associated Person or Company preserved. We pre-create the Freshsales pipeline and stage names to match CentralStationCRM's deal pipeline structure before migration, because Freshsales requires the pipeline to exist before Deal records can be imported. Closed-won and closed-lost status from CentralStationCRM map to Freshsales Deal status values.

CentralStationCRM Lead records (pre-contact prospects stored separately from Deals) map to Freshsales Lead. If the customer has Lead records in CentralStationCRM, we migrate them as Freshsales Lead records and configure the lead-conversion mapping (Admin Settings > Leads module) so that the conversion action creates a matching Contact and Account. The lead_conversion mapping must be pre-configured in Freshsales before migration begins.

CentralStationCRM Activities (calls, meetings, notes) attached to People or Companies are exported via nested routes (GET /api/people/{id}/activities.json). We split the activity type at migration time: call activities map to Freshsales Task with TaskSubtype set to Call; meeting activities map to Freshsales Appointment (Event) with StartTime, EndTime, and Location preserved. Each activity links to the parent Contact or Account via the WhatId field. Activity timestamps are preserved to maintain the chronological timeline in Freshsales.

CentralStationCRM Tasks attached to People or Deals map to Freshsales Task with title, due date, and completion status preserved. Completed status maps to Freshsales status values. Task assignment uses the owner email to resolve against Freshsales User records. We export task titles and due dates; completion state migrates as a status field rather than a hard delete to preserve the history of completed tasks.

CentralStationCRM Offers (standalone quote-like objects with line items and totals linked to People or Companies) map to Freshsales Quote. We pre-create the Freshsales product catalog entries to match the CentralStationCRM offer line items, then map offer headers and line item totals to the Freshsales Quote object. The Quote is linked to the corresponding Freshsales Deal and Contact or Account.

CentralStationCRM Address records exist as 1-n children of People and Companies, fetched via GET /api/people/{id}/addrs.json and GET /api/companies/{id}/addrs.json. We traverse each nested address route during export and write the data to the appropriate address fields on the Freshsales Contact (for People addresses) or Account (for Company addresses). Multiple addresses per record are handled by populating the primary address fields and storing additional addresses in a custom text field formatted as a multi-line string.

CentralStationCRM flat tag labels applied to People, Companies, Deals, and Offers map to Freshsales Labels where supported (Contacts, Accounts, Deals). Tags applied to Leads do not have a native Freshsales equivalent; we store them in a custom multi-select text field on the Lead record. We preserve the full tag vocabulary as-is, without transformation, and apply Labels at the destination after the parent record is created.

CentralStationCRM tenants define their own custom fields with no fixed schema across accounts. We discover all custom fields at the source during scoping, map each to a Freshsales custom field of the appropriate type (text, number, date, dropdown, multi-select) pre-created in the destination Admin Settings, and apply the mapping in the migration transform. Freshsales requires custom fields to exist in the destination before records containing those field values are imported; we coordinate this order explicitly.