Migrate from Star CRM to Freshsales

Star CRM's primary record type is Contact, which may include both unqualified prospects and converted customers. Freshsales separates these into Lead (unqualified prospects) and Contact (qualified buyers attached to Accounts). We assess each Star CRM Contact record during discovery and split based on any lifecycle, status, or stage property observed in the live API response. Unqualified records land in Freshsales Lead; records with an associated Company and active Deal land in Freshsales Contact under an Account.

Star CRM Company records map directly to Freshsales Account. We use company name as the dedupe key during import. Account is imported first so that the Contact-to-Account relationship is satisfied at the moment of Contact insert. Any phone, website, industry, or address fields observed in the Star CRM schema map to the corresponding Freshsales Account field.

Star CRM Deals map to Freshsales Deals with stage, value, owner, and currency preserved. Pipeline stage names from Star CRM are mapped to Freshsales stage values during the scoping call. If Star CRM used a single pipeline, we create one Freshsales pipeline; if multiple pipelines are observed, we create corresponding Freshsales pipelines from the Blossom tier onward.

Each Star CRM pipeline stage maps to a Freshsales Deal stage. We define stage probabilities during scoping so that they reflect the historical close rates observed in Star CRM. Freshsales allows stage customization from Admin Settings without code; we configure this before the Deal import phase begins.

Star CRM Activities (calls, emails, meetings, notes) map to Freshsales Task or Event records linked to the parent Contact or Deal. Date formats are normalized to ISO 8601 during transform. Call disposition and duration fields observed in Star CRM become custom fields on the Freshsales Task record.

Where Star CRM distinguishes a Lead record type from Contact, these migrate directly to Freshsales Lead. Lead source, status, and any scoring values observed in the Star CRM schema become Freshsales Lead custom fields. The Freshsales Lead conversion mapping (Admin Settings > Leads module > Field mapping) is configured during the schema build phase so that converted Leads populate the correct Account, Contact, and Deal fields.

Star CRM custom fields on any object require field-level mapping work. We read the actual field structure during live API discovery (since Star CRM has no public schema documentation) and document every custom property name, type, and value before mapping. Custom fields are pre-created in Freshsales under Admin Settings > Custom Fields before any record data is loaded.

Star CRM User records (name, email, role) map to Freshsales User. We match by email address during migration. Any Star CRM user without a corresponding Freshsales User is held in a reconciliation queue for the customer's admin to provision before the Deal import phase. Owner assignment on Deals and Activities resolves through this User mapping.

Star CRM tags stored as multi-checkbox properties migrate to Freshsales tags. Multi-select tags may become multi-select picklist fields depending on the target object in Freshsales. We preserve tag names and apply them consistently during import.

Star CRM exports attachments as individual files per record with no structured archive. We download all files, build a manifest linking each file to its parent record ID (Contact or Deal), and re-associate them in Freshsales during upload. This step adds time to projects with heavy attachment volume.