Close to Salesforce migration
We migrate Leads, Contacts, Opportunities, and engagement history from Close into Salesforce Sales Cloud with the Lead-versus-Contact-versus-Account split resolved during scoping, the full activity stream preserved through the Salesforce Bulk API, and every Close Custom Field mapped to a typed Salesforce field before cutover.
FlitStack AI migrates leads, contacts, accounts, opportunities and record type + sales process from Close to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

What moves from Close to Salesforce?
Moving from Close to Salesforce Sales Cloud is a structural migration, not a record copy.
Read the full summary
Close collapses prospects into a unified Lead-Contact model, while Salesforce separates unqualified prospects (Lead), qualified buyers (Contact), and business entities (Account). We resolve that three-part split using Close's status field and contact-to-company relationship during the scoping phase, then pre-create the Salesforce schema — including Custom Objects, Record Types, and stage-probability maps — before any data loads. Activity history (calls, emails, SMS, tasks) must come through the Bulk API because Close's CSV export intentionally omits all activity data. Workflows on Growth and Scale plans do not migrate; we deliver a written inventory of every active Workflow for the customer's admin to rebuild in Salesforce Flow. Custom Activities and Custom Objects require a three-phase dependency pipeline that we execute in strict order to avoid validation errors at insert time.
Lead → Lead
Close Leads with a status indicating they are not yet qualified to a company map directly to Salesforce Lead.
How it maps
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.
Contact → Contact
Close Contacts map to Salesforce Contact.
How it maps
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.
Company → Account
Close Company records map directly to Salesforce Account.
How it maps
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.
Opportunity → Opportunity
Close Opportunities map to Salesforce Opportunity.
How it maps
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.
Pipeline → Record Type + Sales Process
Each Close pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values.
How it maps
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.
Activity: Call → Task (TaskSubtype = Call)
Close call activity records migrate to Salesforce Task with TaskSubtype set to Call.
How it maps
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.
- LeadLead1:1
- ContactContact1:1
- CompanyAccount1:1
- OpportunityOpportunity1:1
- PipelineRecord Typetransformed
- Activity: CallTask1:1
+ 6 more in the mapping below
How Close and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Close | Salesforce |
|---|---|---|
| Prospect vs Account model | Unified Lead and Contact with optional company link; no separate Account object | Separate Lead (unqualified), Contact (qualified), and Account (business entity) objects with explicit convert action |
| Pipeline structure | Unlimited pipelines on all tiers with stage probability and ordering per pipeline | Record Types and Sales Processes with stage whitelisting; unlimited at all paid tiers |
| Custom object availability | Custom Activities and Custom Objects on Growth ($99/seat) and Scale ($139/seat) plans | Custom Objects from Professional tier ($25/user for Sales Cloud Essentials) without setup fees |
| Pricing model | Per-seat from $9 to $149/month; calling features and Workflows require Growth or Scale | Per-user from $25/month on Essentials; unlimited at higher tiers with tiered feature gating |
| Workflow automation | Trigger-based Workflows on Growth and Scale only; Smart Views for saved searches | Salesforce Flow with record-triggered, scheduled, and screen flow variants from Professional |
| Calling and SMS | Native Power Dialer, Predictive Dialer, and SMS on all tiers except Solo | Requires Salesforce Engage, a CTI integration, or a third-party VoIP partner |
| Activity timeline | JSON-only export preserves call, email, SMS, and task history; CSV export silently drops it | Task and Event objects with EmailMessage for emails; CallRecordingContentNote for call audio |
What to watch for in a Close to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
CSV export silently drops all activity history
Close's CSV export format intentionally omits call, email, SMS, and task activity records.
How we handle it
Any customer who has prepared their data via CSV export will have an empty activity history in the migration file. We always request JSON export from Close for activity-bearing records. During scoping we explicitly ask whether the customer has used CSV or JSON exports, and if CSV was used we require a fresh JSON export before migration scoping begins. Failing to catch this results in zero engagement history in Salesforce regardless of how comprehensive the rest of the migration is.
Smart Views only export from the Leads tab
Close's export button only appears for Smart Views created in the Leads tab.
How we handle it
Smart Views built from the Contacts tab produce no export UI. We bypass this entirely by querying Leads and Contacts directly via the Close API rather than relying on saved Smart View exports. However, if a customer has structured critical saved views in the Contacts tab and relies on those for deduplication, we flag this during scoping so the customer can identify which views to translate into Salesforce saved searches post-migration.
Custom Activities require strict dependency ordering
A Close Custom Activity Type must exist before any Custom Field scoped to that type, and both must exist before any activity instance can be imported.
How we handle it
Attempting to import in the wrong order returns validation errors that block the batch. We implement Custom Activity migration as a three-phase pipeline: create type, create type-scoped Custom Fields, then import activity records. If the customer has multiple interdependent Custom Activities we sort them by dependency chain and execute sequentially.
Close Workflows do not migrate to Salesforce Flow
Close Workflows (automated triggers, steps, and goals sequencing outreach) are only available on Growth ($99/seat) and Scale ($139/seat) plans.
How we handle it
They contain rule logic tightly coupled to Close's event model and have no direct Salesforce Flow equivalent. Workflows on the customer's Essentials plan cannot be migrated regardless because the feature tier does not support them. We do not migrate Workflows as code. We deliver a written inventory of every active Close Workflow with its trigger conditions, actions, and a recommended Salesforce Flow equivalent for the customer's admin to rebuild post-migration.
Salesforce validation rules and field-level security block bulk imports
Salesforce orgs commonly enforce validation rules (required formats, conditional requireds, picklist whitelists) and field-level security that the migration user must explicitly bypass during data load.
How we handle it
We coordinate with the customer's Salesforce admin to grant the migration user the necessary permissions and either temporarily disable blocking validation rules during load or add a migration-context bypass check to each rule. Skipping this step typically results in 5-30 percent record rejection on the first import attempt and requires a corrective re-import run.
How the migration runs
Discovery and export audit
We audit the Close account across tier (Solo/Essentials/Growth/Scale), Custom Activities, Custom Objects, pipeline count, active Workflows, and activity volume.
What this step covers
We request a JSON-format export confirmation from the customer to verify that engagement history will be present in the export. We pair this with a Salesforce edition decision: Essentials ($25/user) covers most migrations without custom objects; Professional ($75/user) is required for custom objects and advanced workflow; Enterprise ($165/user) is required for record-triggered Flow at scale, advanced reporting types, or territory management. The discovery output is a written migration scope document and Salesforce edition recommendation.
Schema design and dependency mapping
We design the destination schema in Salesforce.
What this step covers
This includes provisioning Custom Objects (with __c API names matched to Close names), custom fields (type-mapped to Salesforce field types), Record Types (one per Close pipeline), Sales Processes (stage whitelist per Record Type), Page Layouts, and the Lead-Contact-Account split rule based on the customer's Close contact-to-company relationships. Schema is deployed to a Salesforce Sandbox first for validation. If the customer uses Custom Activities, we sequence the schema creation as a dependency chain before any data migration begins.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox using production-like data volume.
What this step covers
The customer's RevOps lead reconciles record counts (Leads in, Contacts in, Accounts in, Opportunities in, Activities in), spot-checks 25-50 random records against the Close source, and signs off the schema and mapping before production migration begins. Any mapping corrections — field type mismatches, picklist value gaps, required field gaps — happen in Sandbox, not in production.
Owner reconciliation and User provisioning
We extract every distinct Close user referenced on Lead, Contact, Opportunity, and activity records and match by email against the Salesforce destination org's User table.
What this step covers
Owners without a matching Salesforce User go to a reconciliation queue. The customer's Salesforce admin provisions missing Users (active or inactive depending on whether the original Close user is still active). Migration cannot proceed past this step because OwnerId references are required on most standard objects.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Close Companies), then Contacts (with AccountId resolved), then Leads (with status-based split applied), then Opportunities (with RecordTypeId and OwnerId resolved), then Custom Objects (sorted by interdependency), then Custom Activities (three-phase pipeline), then Activity history (Tasks, Events, EmailMessages via Bulk API 2.0), then Attachments.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. Bulk API 2.0 chunking handles large activity volumes with exponential backoff on API limit responses.
Cutover, validation, and Workflow rebuild handoff
We freeze writes in Close during cutover, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record.
What this step covers
We deliver the Workflow inventory document to the customer's admin team with a recommended Salesforce Flow equivalent for each active Workflow. We support a one-week hypercare window where we resolve reconciliation issues raised by the sales team. We do not rebuild Close Workflows as Salesforce Flow inside the migration scope; that is a separate engagement.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom object count, and workflow rebuild scope. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Close to Salesforce →Why teams move from Close to Salesforce
- Teams needing native Slack integration, advanced reporting across territories and product lines, or deep ERP and CPQ connectivity outgrow Close's deliberately lean feature set. Salesforce's AppExchange with over 9,000 listings and its native Slack partnership address integration requirements that Close handles through Zapier or API workarounds. G2 and Capterra reviewers cite Close's reporting limitations and lack of native Slack as primary reasons for switching to Salesforce.
- Close's Custom Objects and Custom Activities are only available on Growth ($99/seat) and Scale ($139/seat) plans, and they require strict dependency ordering during any migration. Salesforce supports custom objects from Professional tier ($25/user) without setup fees, which reduces the per-seat cost barrier for data-model-heavy teams that have outgrown Close's lower tiers.
- Salesforce's reporting engine supports multi-dimensional pipeline analysis across territories, product lines, custom fiscal periods, and non-standard attribution models that Close's built-in reporting does not support at the same depth. Enterprise evaluation guides consistently identify Salesforce's analytics as the deciding factor for companies with complex revenue operations requirements.
- Close lacks native Slack integration without a Zapier or API workaround at every pricing tier. Teams relying on Slack for sales team communication and deal alerts find the gap persistent regardless of plan. Salesforce announced a native Slack partnership in 2021 and has deepened the integration across Sales Cloud features including alerts, account timelines, and collaboration workflows.
- Mobile app navigation on Close receives consistent complaints — missed call notifications, the need to reopen the app frequently to stay current, and refresh friction. Salesforce Mobile App with Lightning Experience has received significant investment since 2020 and is the primary interface for field sales teams requiring real-time pipeline access on mobile devices.
Questions, answered
Close to Salesforce migration questions
How long does a Close to Salesforce migration take?
Most migrations land between four and six weeks for accounts under 25,000 Contacts and 5,000 Opportunities with no Custom Activities or Custom Objects and a clean export in JSON format. Migrations with Custom Activities, Custom Objects, multiple pipelines, large engagement histories (over 500,000 activity records), or a destination org with complex existing validation rules move to ten to sixteen weeks because of the three-phase schema pipeline, Bulk API time, and Salesforce org security coordination.
Do my Close Workflows migrate to Salesforce Flow?
No. Close Workflows (automated triggers, steps, and goals that sequence outreach) are only available on Growth and Scale plans and contain rule logic tightly coupled to Close's event model. Salesforce Flow uses a different automation architecture with record-triggered, scheduled, and screen flow variants. We do not migrate Workflows as code. We deliver a written inventory of every active Close Workflow with its trigger, conditions, actions, and a recommended Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds them post-migration. Smart View filters do not migrate either; we document them as a named list for the admin to recreate in Salesforce as saved searches.
Will we lose our call recordings and SMS history?
No. Call recordings in Close are stored as audio files accessible via the API. We download them and re-upload them to Salesforce as ContentDocument records linked via ContentDocumentLink to the matching Call Task. SMS message history migrates as Task records with TaskSubtype set to SMS and the message body preserved in a custom field. Both require the JSON export format from Close; CSV export omits all activity data including calls and SMS. If the customer has only used CSV exports, we require a fresh JSON export before migration scoping begins.
Can we migrate from Close Solo or Essentials where Workflows are not available?
Yes. Close Solo ($9/seat) and Essentials ($49/seat) do not include Workflows, so there are no automation rules to inventory or rebuild. The migration scope is simplified to record migration only: Leads, Contacts, Companies, Opportunities, Custom Fields, and activity history. Custom Activities and Custom Objects are also not available on these tiers, further reducing scope. This typically results in a shorter timeline and lower migration cost than Growth or Scale tier accounts.
How do we handle the Lead versus Contact versus Account split?
Close does not have a separate Account object — Contacts optionally link to a Company record. Salesforce requires Accounts as parent entities for Contacts. We resolve this at migration time: every Close Company becomes a Salesforce Account first; every Close Contact with an associated Company gets the AccountId set during Contact import; Contacts with no Company become Salesforce Contacts without an Account (orphaned contacts are flagged for the admin to either merge or assign to a placeholder Account). Close Leads map directly to Salesforce Leads with status preserved.
Do Custom Activities and Custom Objects migrate automatically?
Custom Activities and Custom Objects migrate but require a three-phase dependency pipeline that must execute in strict order: first we create the Custom Object schema in Salesforce, then we create the custom fields on that object, then we import the records. Attempting to import before the schema is complete returns validation errors. If the customer has multiple Custom Objects with interdependencies, we sort them by dependency chain and create parents before children. This sequencing is manual and is a primary reason Custom Activity and Custom Object migrations extend timelines compared to standard record migration.
Can FlitStack AI migrate our Close data to a multi-org Salesforce structure?
Yes. If the customer maintains separate Salesforce orgs for distinct business units or geographies, we can migrate Close data into multiple destination orgs with appropriate scoping per org. Each org receives its own schema design, sandbox validation, and production migration. Multi-org migrations extend timelines proportionally and require the customer to clearly define which Close records map to which destination org before scoping begins. We do not sync between Salesforce orgs post-migration; that requires a separate integration or Salesforce-to-Salesforce sync configuration.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → SuiteCRM to SalesforceMapping · history · rollbackJobber to SalesforceMapping · history · rollbackHighrise to SalesforceMapping · history · rollbackBitrix24 to SalesforceMapping · history · rollbackSugarcrm to SalesforceMapping · history · rollbackAttio to SalesforceMapping · history · rollback Close to monday CRMMapping · history · rollbackClose to HubSpotMapping · history · rollbackClose to Zoho CRMMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from Close to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote