Migrate from Onsite CRM to Freshsales

Onsite CRM contact records map directly to Freshsales Contact. Standard fields (name, email, phone, company association) map to Freshsales Contact fields: first_name, last_name, email, phone, and the account_id lookup. Email serves as the dedupe key during import. We flag any contact records missing an email address for manual review because Freshsales requires a valid email for the contact to function fully in marketing and AI features.

Onsite CRM company records map to Freshsales Account. The company name becomes the account_name, and the domain or website field maps to Freshsales website. We create accounts before contact import so that account_id lookup is satisfied at the moment of contact insert. If Onsite CRM exposes industry or employee count fields, we map those to Freshsales custom fields created during the configuration phase.

Onsite CRM deal records map to Freshsales Deal. We map deal name, deal value, close date, and stage to Freshsales Deal fields. The stage name from Onsite CRM maps to a Freshsales pipeline stage that we configure before migration, preserving stage order and probability percentage. Closed-won and closed-lost statuses from Onsite CRM transfer to Freshsales deal status values.

Onsite CRM custom pipeline stages are customer-specific and exported as part of the deal export or visible in the pipeline configuration UI. We extract stage names, their display order, and probability percentages. In Freshsales, we configure a matching pipeline with stages named to match the Onsite CRM taxonomy, and set probability mapping per stage. The customer reviews and approves the stage mapping before migration loads begin.

Onsite CRM call logs (built-in calling feature) map to Freshsales Activity records with activity_type = call. Call duration, disposition, and timestamp migrate to Freshsales activity fields. We note that Onsite CRM's call recording storage may be file-based rather than record-based; recording URLs require separate file extraction if the recordings are stored in the Onsite CRM environment rather than a linked telephony provider.

Onsite CRM SMS thread records map to Freshsales Activity with activity_type = task and a custom field sms_body__c carrying the message content. Thread ordering is preserved by setting activity_date to the original message timestamp. We flag SMS export completeness as a pre-migration risk because Onsite CRM's SMS history export coverage may vary by customer configuration.

Onsite CRM email marketing and email tracking records map to Freshsales Activity. The email subject, body, and send timestamp migrate. Freshsales supports email logging through its email logging feature, which we configure during the migration setup phase to match Onsite CRM's email tracking behavior.

Onsite CRM task records migrate to Freshsales Task with title, due_date, status, and priority preserved. Task assignment requires owner resolution: we match Onsite CRM owner email to Freshsales User email and set the owner_id accordingly. Any Onsite CRM task with an unresolvable owner is flagged for the customer to map manually before import.

Onsite CRM custom fields on any object require manual mapping during scoping because the platform exposes only what the UI shows per customer configuration. We request customer-supplied screenshots of the Onsite CRM field configuration page during discovery, then create equivalent custom fields in Freshsales before migration. Field type mapping (text to text, date to date, picklist to picklist) is resolved during scoping, and any Onsite CRM field type that Freshsales does not support natively is flagged for alternative handling.

Tags applied to Onsite CRM contacts or deals migrate as Freshsales Tag records linked to the corresponding contact or deal. The tagging taxonomy is preserved as-is, and the customer reviews tag normalization during scoping. If Onsite CRM uses a flat tag list and Freshsales supports hierarchical tags, we flag the normalization options for customer decision.