Migrate from Close to Freshsales

Close Leads migrate to Freshsales Leads with all standard fields (name, email, phone, status, owner) and all Lead-scoped Custom Fields preserved. We resolve Close lead status labels to Freshsales Lead Status values during the transform. A close_lead_id__c field stores the original Close Lead ID for audit and reconciliation. The mapping excludes any Custom Activity fields that are scoped to Lead in Close; those require the Custom Activity collapse described below.

Close Contacts that carry an organisation name split into a Freshsales Account (the company record) and a Contact linked to it. The Contact-Account relationship is resolved at migration time: we create the Account first using the organisation name from Close, then create the Contact with AccountId pointing to the resolved Account. Contacts without an organisation name in Close migrate as standalone Freshsales Contacts with no Account association.

Close Opportunities map to Freshsales Deals. The Close pipeline_stage maps to Freshsales Deal stage. We create a Freshsales Sales Flow (pipeline) matching the Close Pipeline name and recreate all stage values in order before importing Deals so that the stage reference is satisfied at insert time. Closed-Lost and Closed-Won status from Close map directly to Freshsales deal_status values.

Each Close Pipeline becomes a Freshsales Sales Flow with the same name and stage ordering preserved. Stage probability percentages from Close migrate to Freshsales stage weights. The Sales Flow must exist in Freshsales before any Deal referencing it is imported; we create all Sales Flows in the schema setup phase before any record-level migration begins.

Close pipeline stages map to Freshsales Sales Flow stage values with display order preserved. If a Close pipeline stage has a probability weight set, we create a corresponding Freshsales stage with the probability value. Custom stage columns from Close (such as required_fields_on_entry or custom_probability_override) are noted in the migration scope but cannot be replicated in Freshsales without manual configuration by the admin.

Close's activity stream is only complete via JSON export; CSV export silently omits all activity records. We extract the full activity array from Close's JSON export, transform each entry by type, and import into Freshsales. Call engagements become Task records with TaskSubtype=Call and a custom call_disposition__c field. Email engagements become Task records with a notes_body field carrying the email body. SMS engagements become Task records with a custom sms_direction__c field. Meeting engagements become Event records with StartDateTime and EndDateTime preserved. All tasks link to the parent Contact or Lead via the WhoId resolution built during record creation.

Close Custom Activities have no Freshsales equivalent; Freshsales does not support user-defined activity type schemas. We collapse all Custom Activity instances into Freshsales Task records and set a custom field activity_type__c to the original Close Custom Activity Type name so that the activity kind is preserved in the timeline. The Custom Activity Type definitions are exported as a schema document and included in the handoff package for the customer's admin to review.

Close Lead Custom Fields, Contact Custom Fields, and Opportunity Custom Fields map to Freshsales Lead, Contact, and Deal Custom Fields respectively. We read the field definition (type, picklist options, required flag) from the Close API, create the equivalent typed field in Freshsales via Admin Settings before import, and preserve choice-option labels exactly. If a Close custom field type has no direct Freshsales equivalent (for example, a formula field), we flag it in the scope document and note whether the value can be replicated post-migration in Freshsales.

Close Users map to Freshsales Users by email address match. We extract all distinct users referenced on Lead, Contact, Opportunity, and Activity records and match against the Freshsales User table. Any Close User without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before the record migration phase begins. Role and team membership from Close are noted but do not replicate; Freshsales role-based access is configured by the admin post-migration.

Close Smart Views (saved Lead search filters) cannot be exported as data and have no direct Freshsales equivalent. We extract the Smart View filter configuration as a named JSON document and deliver it to the customer's admin as a step-by-step guide for recreating the same filters as Freshsales Saved Views. Filter logic translation is included: Close operator types (is, is_not, contains, etc.) map to Freshsales filter operators one-to-one.