Migrate from Close to Salesforce Sales Cloud

Close Leads with a status indicating they are not yet qualified to a company map directly to Salesforce Lead. Standard fields (name, email, phone, status, owner, created_at, updated_at) map 1:1. Close's lead_status property maps to Salesforce Lead Status picklist. Any Lead Custom Fields migrate as custom fields on the Salesforce Lead object. We use the Close API to export Leads rather than relying on Smart View CSV exports, which are only available from the Leads tab.

Close Contacts map to Salesforce Contact. Each Close Contact carries a direct link to a Close Company record. We resolve this at migration time: if the Contact has an associated Company, we create the corresponding Salesforce Account first, then attach the Contact via AccountId. If the Contact has no Company, it becomes a Salesforce Contact without an Account. Email, phone, owner, and all Contact Custom Fields migrate 1:1.

Close Company records map directly to Salesforce Account. Company name becomes Account Name, domain becomes Website, industry and address fields map to their Salesforce counterparts. Account is created before any Contact import so the AccountId lookup is satisfied at the moment of Contact insert. Close Company Custom Fields migrate as custom fields on the Salesforce Account object.

Close Opportunities map to Salesforce Opportunity. The Opportunity amount, stage, expected close date, and owner migrate 1:1. The Close pipeline reference maps to a Salesforce Record Type that we configure before migration, with the pipeline stage mapping to the corresponding Sales Process stage. Closed-Lost and Closed-Won dates migrate to Salesforce's CloseDate and IsClosed fields.

Each Close pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from Close to Salesforce StageProbability, rounded to the nearest integer. Stage ordering is preserved by setting the picklist value order in the destination.

Close call activity records migrate to Salesforce Task with TaskSubtype set to Call. Call disposition, duration, and recording URL migrate to custom Task fields. The WhoId points to the migrated Lead or Contact; the WhatId points to the related Opportunity or Account. ActivityDate is set to the original Close timestamp to preserve timeline ordering.

Close email activity records migrate to Salesforce EmailMessage (the email body and headers) linked to an Activity Task (the timeline entry). The WhoId on Task points to the migrated Lead or Contact. Email thread IDs are preserved to maintain conversation threading in Salesforce.

Close SMS activity records migrate to Salesforce Task with TaskSubtype set to SMS. The message body and direction (inbound/outbound) migrate to custom Task fields. The WhoId points to the migrated Lead or Contact. SMS is not a standard Salesforce Task subtype; we configure a custom TaskSubtype value or use a custom field for SMS-specific data if the org does not have TaskSubtype enabled.

Close task activity records map directly to Salesforce Task. Status, Priority, due date, and assigned owner migrate 1:1. Owner resolution uses the email-based User mapping established during owner reconciliation.

Close Custom Activities are user-defined activity types with their own field schema. Migration requires a three-phase pipeline: first, we create a Salesforce Custom Object matching the Custom Activity Type name with a __c suffix. Second, we create all type-scoped custom fields on the new object. Third, we import the activity records against the pre-created schema. This ordering is strict — attempting to import before the schema is complete returns validation errors.

Close Custom Objects are fully user-defined record types. Migration follows the same three-phase pipeline as Custom Activities: create the Salesforce Custom Object with matching API name, create all custom fields including lookup relationships to standard objects, then import the records. If a Custom Object has a lookup to another Custom Object, we sort by dependency and create the parent first.

Attachments on Close Leads and Contacts are downloaded via the Close API as binary files. We re-upload them to Salesforce as ContentVersion records linked via ContentDocumentLink to the migrated Lead or Contact. The attachment filename and any associated notes migrate as the ContentDocument Description field. Large attachments (over 25 MB) require chunked upload via the Salesforce ChunkedFileProcessor.