Skip to content
Get a quote

Migrate to Salesforce

Salesforce is the platform-as-CRM destination whose migration difficulty is driven by External IDs, async loader job mechanics, and the Apex/Flow/Validation Rule stack that fires on every imported row.

Short answer

FlitStack AI migrates pipelines, contacts, and deals into Salesforce from 850+ CRMs, including HubSpot, Mailchimp, Zoho CRM, Act!. Every field is mapped to Salesforce's objects, history and associations come across, the Salesforce setup is configured alongside, and the whole migration stays reversible in one click.

By

From Any source
DestinationSalesforce
HubSpotMailchimpZoho CRMAct!GoldMine
850+ sources mapped into Salesforce

Systems we move into Salesforce

The CRMs teams most often move from. Each page shows what moves, the field mapping and what to watch for.

HubSpot to SalesforceMailchimp to SalesforceZoho CRM to SalesforceAct! to SalesforceGoldMine to SalesforcePipedrive to SalesforceAttio to SalesforceSugarcrm to SalesforceBitrix24 to SalesforceClose to SalesforceSuiteCRM to SalesforceJobber to SalesforceHighrise to SalesforceTwenty CRM to SalesforceBlackbaud to SalesforceActiveCampaign to SalesforceFreshsales to Salesforcemonday CRM to SalesforceCustomer.io to SalesforceHoneyBook to SalesforceFotoNotes to SalesforceHousecall Pro to SalesforceDaylite to SalesforceConvertkit to SalesforceCopper to SalesforceSuperOffice CRM to SalesforceZendesk Sell to SalesforceInsightly CRM to SalesforceServiceTitan to SalesforceLeadSimple to SalesforceAweber to SalesforceDynamics 365 to SalesforceSnovio to SalesforceClio to SalesforceDubsado to SalesforceOdoo CRM to SalesforceSendCloud to SalesforceAutoText to SalesforceSpotler CRM to SalesforceHighLevel to SalesforceYardi to SalesforceMarketing Star to SalesforceKartra to SalesforceCivicrm to SalesforceSentia to SalesforceWise Agent to SalesforceKeap to SalesforceIterable to SalesforceMoEngage to SalesforceJobnimbus to SalesforceSysteme IO to SalesforceBigin by Zoho CRM to SalesforceSage CRM to SalesforceCision to SalesforceSharpspring to SalesforceSuiteDash to SalesforceTeamleader to SalesforceEspoCRM to SalesforceNimble CRM to SalesforceMautic to SalesforcePodio to SalesforceBlinQ to SalesforceAdobe Campaign to SalesforceOntraport to SalesforceVendasta to SalesforceBoomTown to SalesforceAccelo to SalesforceCliniko to SalesforceKlipy CRM to SalesforceChartMogul to SalesforceTekion to SalesforceFreeCRM to Salesforce

What Salesforce supports, and where its import tools stop

  • The AppExchange marketplace with 5,000+ prebuilt apps gives enterprises integrations for nearly every business workflow without custom development.
  • Native Einstein AI for lead scoring, opportunity insights, and predictive forecasting adds intelligence without a separate platform purchase.
  • Territory management, multi-currency support, and advanced forecasting satisfy the needs of complex B2B sales organizations with structured revenue teams.
  • Slack, Tableau, and CPQ are deeply integrated into the core platform, keeping the sales stack unified for teams already in the Salesforce ecosystem.
Bulk APIOAuth 2.0 (Connected Apps, JWT, or Session ID)
Rate limits100,000 daily API requests base for Enterprise, plus 1,000 requests per user license; concurrent long-running requests capped at 25; individual call timeout 10 minutes
ObjectSupportNote
AccountsfullThe primary company/customer record in Salesforce. Standard fields (Name, Industry, Annual Revenue, Type) are stable and map cleanly. Parent-Account hierarchies must be sequenced — we import parent Accounts first, then children. Supports custom fields freely.
ContactsfullPerson-level records linked to Accounts via a many-to-many Account Contact Relation junction object. We import Contacts after Accounts are committed and map the junction table as a second pass. Supports custom fields and direct Owner assignment.
LeadsfullUnqualified prospects tracked before conversion. Contains LeadSource, Status, Rating, and custom fields. Conversion creates an Account, Contact, and optionally an Opportunity — we handle both migrated Leads and their post-conversion artifacts.
OpportunitiesfullThe core deal record with Stage, Amount, Close Date, and Probability. Multi-currency and negative Amounts are supported natively. We import after Accounts exist; Opportunity Contact Roles and Opportunity Team Members are separate passes.
CasesfullSupport tickets with Status, Priority, Origin, and Contact/Account linkage. Supports custom fields and entitlement association. Cases with open Activities must have those Activities imported separately after the parent Case.
CampaignsfullMarketing initiative containers with Budget, Status, and Type. Campaign Members track individual Contact or Lead responses. We import Campaigns first, then Campaign Members in batches against the Bulk API quota.
ContractsfullLegal agreement records with Start Date, End Date, Contract Term, and Status. Linked to an Account and optionally to a primary Contact. Contract Line Items are a separate object and require separate mapping.
OrdersmappedOrder records exist on top of Opportunities and Contracts. Status, Effective Date, and Order Products must all map correctly. If the org uses Advanced Order Management or Revenue Cloud, order lineage and related asset creation require additional handling beyond a standard flat import.
Products (with Price Books)mappedProducts are the catalog items; Price Book Entries link them to Price Books with pricing. Opportunity Line Items reference Price Book Entries. We map Products first, then Price Book Entries, then Opportunity Products — a three-pass sequence. Custom pricing on line items requires field-level mapping.
QuotesfullQuote records linked to Opportunities, carrying line items and pricing. Quote Line Items reference Products and Price Book Entries. We import Quotes after Opportunities are in place and before finalizing order conversion.
AssetsfullPost-sale product ownership records linked to Accounts and Contacts. Serial Number, Status, Install Date, and Quantity map cleanly. Assets created automatically from Contracts or Orders require the parent records to exist first.
Custom ObjectsmappedFully supported via the Metadata API for schema discovery and the Bulk API / Composite API for data migration. Each Custom Object may have its own dependency chain — we audit relationships before sequencing the import. Naming conventions (MyObject__c) are preserved in the destination.
Activities (Tasks and Events)mappedTasks and Events are individual activity records linked to any Who or What object (Contact, Lead, Account, Opportunity). They do not exist in a hierarchy, but open Tasks against deleted parent records will fail to insert — we filter or flag these during validation.
Account Teams and Opportunity TeamsmappedTeam member junction records that assign User IDs to an Account or Opportunity with a specific role. We import these after the parent Account or Opportunity and after all relevant User records exist in the destination. Sequential ordering by Team Member ID is not guaranteed, so we batch and upsert by External ID.

The Salesforce migration guide

Why teams migrate to Salesforce

The four shapes a Salesforce migration takes, and what makes the platform harder — or easier — than the category average.

Salesforce, Inc. was founded by former Oracle executive Marc Benioff in March 1999 and is headquartered in San Francisco, California1. For fiscal year 2026 the company reported $41.5 billion in annual revenue, and Sales Cloud sits at the centre of a broader stack that includes Service Cloud, Marketing Cloud, Revenue Cloud, Tableau, Slack and the Agentforce AI layer1.

The typical Sales Cloud customer is a mid-market or enterprise revenue team — usually 100 to 10,000+ users — that needs deep customisation through Apex code, Flow, Validation Rules and a Role Hierarchy / Sharing Rules access model. Compared with HubSpot or Pipedrive, Salesforce positions on configurability and ecosystem depth rather than time-to-value; compared with Microsoft Dynamics 365, it positions on the AppExchange marketplace and a wider partner network.

The shapes of migration that actually land on Salesforce fall into four patterns. First, legacy consolidation: spreadsheets, Act!, SugarCRM, on-prem Microsoft Dynamics, or a homegrown SQL database where the source schema is loose and the project is really a re-architecture. Second, competitor exits from HubSpot, Pipedrive, Zoho or Insightly when the customer outgrows the source tier or needs Apex-level customisation1314.

Third, multi-org consolidation, where two or more Salesforce orgs from past M&A activity are merged into one — typically the hardest shape because both sides carry incompatible Record Types, Sharing Rules and Apex Triggers. Fourth, platform standardisation, where a parent enterprise standardises acquired business units onto a single Sales Cloud org.

What makes migrating to Salesforce harder than the category average is the automation that runs on insert. Validation Rules, Apex Triggers, Workflow Rules, Process Builder and Flow all evaluate every imported record, and a workflow that expects a 10-digit phone number breaks the moment legacy data shows up with a country code22. Most migration teams disable automation during the load and re-enable it post-cutover.

What makes it easier than the average is the External ID field type — a first-class upsert mechanism on every object, capped at 25 external IDs per object, that lets you match records by a value from the source system rather than by Salesforce's 18-character Record ID3. Combined with the platform's job-based async loader and the load order discipline that External IDs enforce, the platform rewards teams that plan their upsert keys before writing a single row.

Apex Triggers, Flows, Validation Rules and Reports do not import — they are rebuilt from documentation. Teams that scope for that work up front finish on time; teams that assume parity do not.

The destination has a richer automation layer than the source, and it fires on every imported row unless you actively quiet it.

The Salesforce data model you need to map into

Standard Objects, Custom Objects, Record Types, relationships, and the External ID upsert mechanism — the destination schema decoded.

Salesforce's data model is built around Standard Objects (Account, Contact, Lead, Opportunity, Case, Campaign and others), Custom Objects you define yourself, and a Relationship model that includes Lookups, Master-Detail relationships and Junction Objects for many-to-many cases.

Before you can map a field, you need to know which Standard Object the row belongs on, which Record Type applies inside that object, which required fields the page layout enforces, and which field you will use as the External ID for upsert. The table below summarises the objects you will touch in a Sales Cloud migration.

ObjectWhat it storesRequiredTier
AccountCompanies, households, or person accountsName (or Last Name on Person Accounts)All editions
ContactIndividual people associated with an AccountLast Name, Account ID (unless Individual model)All editions
LeadUnconverted prospects before qualificationLast Name, CompanyAll editions
OpportunityRevenue deals in a sales stage pipelineName, Stage, Close Date, Account IDAll editions
CaseCustomer service / support ticketsStatus, OriginAll editions (Service Cloud for full tooling)
Campaign / CampaignMemberMarketing programs + member junctionCampaign Name; Member needs Lead or Contact IDAll editions
Product2 / Pricebook / PricebookEntrySellable catalogue + price book entriesName, ProductCode; PricebookEntry needs Product + PricebookAll paid editions
OpportunityLineItem / Quote / QuoteLineItemProducts on a deal and quote documentsOpportunityId + PricebookEntryId; Quote needs OpportunityIdAll paid editions
Task / EventActivities — calls, emails, meetings, notesSubject; ActivityDate or StartDateTimeAll editions (Activity object is virtual)16
Custom ObjectsCustomer-defined record typesDefined per object; needs deployed schema before loadEnterprise+ for unlimited; lower editions capped

Salesforce assigns an 18-character Record ID (the canonical primary key) to every record on insert. You cannot set Record IDs on import — they are system-generated. The migration pattern is to use External ID fields instead: up to 25 custom fields per object (auto-number, email, number or text type) that you flag as External ID and use as the upsert match key3.

Mark the External ID as Unique and case-sensitive to prevent silent duplicate merges. The async loader references the External ID by name in the job payload; if the value exists, the row updates, if not it inserts.

Relationships come in three shapes. Lookup is a loose one-to-many — deleting the parent does not cascade. Master-Detail is a tightly-coupled one-to-many where the child inherits ownership and sharing from the master and is deleted with it. Junction Object is a custom object with two Master-Detail relationships used to model many-to-many — OpportunityContactRole is the standard example connecting Opportunities to Contacts. Custom field types determine validation and storage; the catalogue below covers what you can model.

Field typeLimitNotes
Text / Text AreaText 255 chars; Long Text Area 131,072 chars; Rich Text Area 131,072Long Text counts 2 bytes per Unicode character21
Number / Currency / Percent18 digits total; up to 18 decimal placesCurrency respects multi-currency org settings
Date / Date-TimeDate-Time stored in UTC; ISO-8601 on loaderWrong format silently imports as null on Data Import Wizard
Picklist (single / multi-select)1,000 active values; 2,000 inactive on single-selectRestrict picklist enforces strict ENUM — typo = rejection
Formula / Roll-Up SummaryFormula 3,900 char compiled; Roll-Up needs Master-DetailDoes not import — recomputed by platform after load
Lookup / Master-Detail40 lookups per object; 2 Master-Detail max per objectMaster-Detail cascades delete; Lookup does not
External ID fieldsUp to 25 per object (auto-number, email, number, text)Primary upsert mechanism via loader and Data Import Wizard3
Custom fields per object500 on Enterprise; 800 on UnlimitedHard cap; Big Objects + External Objects for overflow

Record Types add a second axis: one Custom Object can have multiple Record Types, each with its own Page Layout, picklist value subset, and required-fields list. A Lead inserted with the wrong Record Type silently displays the wrong fields to the rep on day one — and the value RecordTypeId on every imported row decides which one it lands on.

Custom Objects participate in relationships exactly like Standard Objects, with the same Master-Detail cascade and Junction Object patterns. Big Objects (the platform's archive tier) default to 1 million records — you contact your Account Executive to raise that ceiling, and they are not used for active migration loads11.

Pre-migration prep — the work before you touch Salesforce

What must be true on the source, the destination, and across the team before the first row is loaded.

The single best predictor of a clean Sales Cloud migration is how much work you do on the source side before the first load job is submitted. Practitioners consistently report that field-mismatch breakage is not really about the fields — it is about the Validation Rules, Apex Triggers and Flows that fire on every imported row and reject anything the legacy data does not perfectly match22.

Disable Validation Rules and Triggers during the load, then re-enable and run regression tests. Most migration teams skip the regression step — and pay for it on day five.

Treat the source export as raw material shaped to Salesforce's expected formats — email validated, phone normalised to international format, picklist values converted to the destination's exact case-sensitive values, dates rewritten to ISO-8601, owner emails resolved to Salesforce User IDs.

Source-side prep

  • Audit and dedup the source before export — Cloudingo, DemandTools and Plauti Duplicate Check are the Salesforce-native dedup tools most teams reach for, and they catch fuzzy-match duplicates that Salesforce's built-in Matching Rule and Duplicate Rule will silently merge during insert25.
  • Stamp a stable External ID on every record in the source export — the legacy primary key, a UUID, or a composite key — and create a custom field on each destination object marked External ID + Unique + case-sensitive to land it3.
  • Convert picklist values to the exact destination case — Salesforce restricted picklists enforce strict ENUM matching and reject any typo, casing difference or trailing space with bad value for restricted picklist field. Build a transform table per picklist.
  • Resolve owners by exporting your destination Salesforce User list (User.Id, Username, FederationIdentifier) and joining it to the source owner column. Rows whose OwnerId cannot be resolved fall to the integration user, which silently breaks owner-based Sharing Rules.
  • Decide what is in scope for historical activities. Tasks and Events can be inserted with backdated ActivityDate, but they archive automatically after 365 days and the IsArchived flag is not updatable directly16.

Destination-side prep

  • Create a Full Sandbox (or Partial Copy on lower editions) from Setup → Sandboxes — a Full Sandbox copies production data and metadata for end-to-end dry-runs and the refresh interval is 29 days17.
  • Provision users first, ideally through your identity provider (Okta or Microsoft Entra ID), and assign Permission Sets and Profiles before the load — Apex Triggers reference running user context and ownership assignment silently falls to the integration user if a referenced User does not yet exist.
  • Deploy every custom field, Record Type, Page Layout and picklist value to production via a deployment tool before importing — fields created in the destination after a row arrives cannot be back-populated cleanly.
  • Disable Validation Rules, Workflow Rules, Process Builder Flows and Apex Triggers that should not fire on bulk insert (or wrap them in an Trigger.New.Bypass__c = true skip flag pattern). Re-enable post-cutover with a regression test plan22.
  • Pre-create Pricebooks, PricebookEntries and Products before any OpportunityLineItem load — a Line Item targeting a missing PricebookEntry fails with INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST and the row is rejected.

People prep

Cutover works only when humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours — and communicate it to every department touching the CRM. Train sales reps on Sales Cloud daily workflows, Opportunity stage management and List Views before go-live, not after. A clean legacy-CRM migration of under 25,000 records often lands in a week; a multi-org consolidation with Apex rebuild and Pricebook reconciliation runs four to twelve weeks.

Import mechanisms: Data Import Wizard and Data Loader

Multiple mechanisms in, each with different limits, object support, and async behaviour. Picking the wrong one stalls mid-migration at scale.

Salesforce exposes multiple load paths and the right one depends on dataset size, object mix, and whether you need to re-run idempotently. Data Import Wizard covers small, simple loads on a handful of objects. Data Loader and Workbench cover the medium tier. For programmatic, repeatable and very large loads, Data Loader's async mode (or a third-party iPaaS) takes over. Third-party tools sit on top of all of them.

Data Import Wizard

The native UI tool lives at Setup → Data Import Wizard and supports a deliberately limited set of objects: Leads, Accounts, Contacts, Campaign Members, Solutions, Person Accounts and Custom Objects. It does not support Opportunities, Cases or Products — for those you escalate to Data Loader. The record limit is 50,000 per import, file format must be CSV with UTF-8 encoding (not UTF-8 BOM, not ANSI), and dates must be in the org's locale format.

The Wizard's killer feature is built-in Duplicate Rule + Matching Rule enforcement on Accounts and Contacts — but that same feature silently blocks rows that should pass, so know to set the Allow Duplicates flag explicitly when the source rows are legitimately new25. Use the Wizard for one-shot loads under 50,000 records on supported objects, or any time you want a visual mapping review.

Data Loader and Workbench

Data Loader is the desktop app (Windows/macOS) that ships from Salesforce. It supports every Standard and Custom Object, runs Insert / Update / Upsert / Delete / Hard Delete / Export operations, and supports both interactive and CLI modes for scheduled jobs. Workbench is the browser equivalent — useful for one-off jobs without local install.

Large-volume async loading

For programmatic, repeatable and very large loads, Data Loader can be configured to use the platform's async load mode. The job model is: create an ingest job with operation (insert/update/upsert/delete) and object, upload CSV data, then mark the upload complete to enqueue. Salesforce auto-chunks server-side — you do not size batches yourself.

Per-transaction limits compound on top: 100 SOQL queries and 150 DML statements per transaction — relevant because Apex Triggers firing on your import consume those quotas. Bulk operations also share a daily submission cap, so naive code that submits tiny batches will exhaust the daily allocation27.

Third-party staging tools

Dataloader.io (web Data Loader from MuleSoft), Skyvia, Talend, Informatica Cloud, Jitterbit, MuleSoft Anypoint and ETL platforms like Fivetran, Airbyte and Stitch all handle Salesforce loads. For one-time migrations the value is repeatability under failure and built-in schema mapping; for ongoing syncs they become the system of integration. Most enterprise migrations end up on MuleSoft or Informatica when the source database is on-prem and the company already has an iPaaS licence.

Mapping your data into Salesforce

The longest section — because field mapping plus Record Type plus External ID is where almost every Salesforce migration that fails actually breaks.

Mapping is where every Salesforce migration earns its scars. The schema decisions you make in your mapping spreadsheet determine whether Reports work on day two, whether Validation Rules accept user edits on day five, and whether your sales team trusts the data on day thirty.

Work object by object, top to bottom of the load order: Users first (already done in prep), then Accounts, then Contacts, then Leads, then Opportunities, then OpportunityLineItems, then Tasks/Events, then Custom Objects. Load order matters because every child row needs a parent External ID that already exists.

Account

Common source → Salesforce Account mapping
SourceDestinationNote
company_nameNameRequired (or LastName on Person Accounts)
legacy_account_idLegacy_Account_ID__c (External ID, Unique)Primary upsert key — create this custom field first3
website / domainWebsiteUsed by Duplicate Rule fuzzy match — normalise format
industryIndustryRestricted picklist — map to exact case-sensitive value
annual_revenueAnnualRevenueCurrency; respect multi-currency org if enabled
parent accountParentId (Lookup)Set in a second pass after all Accounts load
ownerOwnerIdResolve to Salesforce User Id; falls to integration user if missing

Contact

Common source → Salesforce Contact mapping
SourceDestinationNote
first_name / last_nameFirstName / LastNameLastName required
emailEmailUsed by Standard Contact Matching Rule for dedup25
phonePhoneNormalise to international format before load22
account_nameAccountId (Lookup)Resolve via Account External ID upsert lookup, not by name
legacy_contact_idLegacy_Contact_ID__c (External ID, Unique)Primary upsert key for re-runs
ownerOwnerIdMap by Username or Salesforce User Id

Opportunity and pipeline stages

Recreate every Sales Process and every Opportunity stage in Salesforce before importing Opportunities. Each stage has a StageName value, a ForecastCategoryName, a numeric Probability and a Boolean IsClosed / IsWon. Stage history is preserved in OpportunityHistory, which is read-only — you cannot insert historical stage transitions directly. To preserve the timeline, populate custom datetime fields like Stage_Entered_Qualification__c from the source.

Opportunities that target a stage value not present in the assigned Record Type's Sales Process are rejected with bad value for restricted picklist field. Map source stages to destination stages explicitly per Record Type.

Common source → Salesforce Opportunity mapping
SourceDestinationNote
deal_nameNameRequired
stageStageNameRestricted picklist by Sales Process per Record Type
amountAmountCurrency; OpportunityLineItems override if used
close_dateCloseDateRequired; YYYY-MM-DD; cannot be null
accountAccountIdResolve via Account External ID lookup
record_typeRecordTypeIdDrives Page Layout + Sales Process — set explicitly
ownerOwnerIdDrives forecasting + Role Hierarchy sharing
legacy_opp_idLegacy_Opp_ID__c (External ID, Unique)Upsert key for re-runs and reconciliation

Custom-field mapping strategy

Resist the urge to map every source custom field one-to-one. Enterprise Edition caps Custom Fields at 500 per object, Unlimited at 800. Migrate only fields used by an active Validation Rule, Apex class, Flow, Report or List View in the last 12 months. Excess fields waste field allocation, slow down Page Layouts and clutter Search results.

For picklist fields where source values do not match the destination, either: (1) extend the destination picklist with the missing values before loading, (2) collapse adjacent values during transform, or (3) introduce a parallel custom Text field that holds the legacy value verbatim. Formula and Roll-Up Summary fields do not import — Salesforce recomputes them on-platform — so any source formula must be rebuilt as a Salesforce formula field after schema deploy.

Historical activities — Tasks, Events, Notes, Emails

Salesforce models activities through the virtual Activity parent object and two concrete children: Task (calls, completed work, to-dos) and Event (meetings)16. Both support backdated ActivityDate and a WhoId (Lead/Contact) and WhatId (Account/Opportunity/Case) lookup pair that places the activity on the related record's timeline.

Critical gotcha: Tasks and Events archive automatically after 365 days, moving to the ArchivedActivity shadow table — and the IsArchived flag is not updatable, so you cannot insert records pre-archived16. Older historical activities sit in live storage until Salesforce's nightly archive job catches up, which means a 5-year activity backfill briefly counts against your full data storage allocation.

Files and attachments

Salesforce has two file frameworks: the legacy Attachment object (25 MB cap per file, no metadata customisation) and the modern Files framework built on ContentVersion + ContentDocument + ContentDocumentLink (10 GB cap per file in Lightning Experience, full metadata support). New migrations should always land on Files.

The migration pattern is: upload a binary as a ContentVersion with the file body as VersionData (base64) and Title, capture the returned ContentDocumentId, then link it to the parent record via a ContentDocumentLink row. For large attachment estates (TBs), most teams keep originals in S3 or Azure Blob and store a deep link in a custom URL field on the Salesforce record — only the most-recent or most-referenced subset inlines.

Audit trail, ownership and original timestamps

By default Salesforce stamps CreatedDate, CreatedById, LastModifiedDate and LastModifiedById on insert and they are read-only. To preserve original audit trail, you submit a one-time support case requesting Create Audit Fields permission, which then lets the loader set those four fields explicitly during insert.

Once enabled, you set CreatedDate and the others in your load payload. The permission applies org-wide and is usually toggled off after migration completes to prevent users from rewriting history. Field History Tracking (which captures per-field change history) supports 20 fields per object by default; Field Audit Trail (paid add-on) extends to 60 fields per object with 10-year retention.

CRM-specific: lead scoring, email/calendar sync, Apex/Flow rebuild

Lead scoring in Sales Cloud is delivered via Einstein Lead Scoring (predictive, AI-trained on your historical conversion data) or via custom scoring formulas. Neither imports from the source — Einstein needs at least 1,000 converted leads in the destination to start scoring, and custom scoring formulas are rebuilt from documentation. If you must preserve historical scores, land them in a Legacy_Lead_Score__c custom number field and let Einstein/your new formula accrue forward.

Apex Triggers, Flows, Process Builder Processes, Validation Rules, Workflow Rules, Approval Processes, Reports and Dashboards do not import — they are rebuilt against the new schema. Process Builder is being end-of-lifed; new automation should land on Flow17. Scope the rebuild before signing the scope.

Email and Calendar sync (Gmail/Outlook via Einstein Activity Capture, or the older Lightning Sync) is configured per user under Setup → Einstein Activity Capture after users and OwnerIds are stable. Enabling it during the import window backfills duplicate emails against the contacts you are still loading.

The pitfalls that derail Salesforce migrations

Specific failure modes — ranked by impact, each tied to the exact Salesforce mechanism that breaks.

Validation and cutover

What to verify after the loader finishes, in what order — and how to fail safely when Triggers ate a chunk.

Validation is the bridge between the loader returning success and users being allowed in. Salesforce data-migration practitioners recommend a three-stage validation: a test load of 10 percent of records in a Full Sandbox with department-rep spot-checks, the full production load with real-time monitoring of partial-success counts, and a 30-day post-migration data-quality audit using DemandTools or Cloudingo to surface the merges the Matching Rule did silently34.

Build a reconciliation queries spreadsheet that compares source and Salesforce on each of the counts below. Anything outside a 0.5 percent variance gets investigated before login access opens.

  • Total Accounts inserted vs source, minus deliberately-excluded rows (test accounts, deactivated, role-based) — use SOQL SELECT COUNT() FROM Account WHERE Legacy_Account_ID__c != null to count only migrated rows.
  • Total Contacts per Account spot-check — pick 20 high-value Accounts and verify Contact counts match source, catches Matching Rule merges that collapsed two distinct prospects.
  • Total Opportunities per Stage per Record Type plus sum of Amount per Pipeline — a non-trivial dollar variance usually signals a stage-mapping error or a currency precision drop on multi-currency orgs.
  • Total Tasks + Events per ActivityDate bucket vs source — confirm backdated ActivityDate round-tripped and the rows did not archive prematurely.
  • OpportunityLineItem rollup: sum TotalPrice per Opportunity vs source line-item total — catches missing PricebookEntry references.
  • OwnerId distribution — SELECT OwnerId, COUNT(Id) FROM Opportunity GROUP BY OwnerId and confirm no record landed on the integration user that should not have.
  • External ID uniqueness — SELECT Legacy_Account_ID__c, COUNT(Id) FROM Account GROUP BY Legacy_Account_ID__c HAVING COUNT(Id) > 1 should return zero rows.

On top of reconciliation, run a manual spot-check protocol: pick 30 random records across objects and verify each field against the source UI. Pick five high-value Opportunities and trace the full graph — Account, Contacts, Line Items, Tasks, Quotes. If a non-trivial discrepancy shows up in three or more of the 30, halt the load, fix the root cause (almost always a Trigger or Validation Rule), and re-import the affected rows by Legacy_ID via Data Loader upsert.

Salesforce's native Recycle Bin holds deleted records for 15 days and can be used for small-scale undo from the UI34. Undoing an Import under Setup is available only for Data Import Wizard imports launched within the last 24 hours and only deletes records the import created34. For Data Loader there is no built-in undo — you delete by Legacy_Import_Batch_ID__c custom field and re-import from the cleaned source.

The rollback strategy practitioners actually use: full org backup via Salesforce Data Export (Setup → Data Export) or a third-party backup tool like Odaseva or OwnBackup before the migration starts, plus stamping every imported row with an Import_Batch_ID__c custom text field, so catastrophe means a SOQL delete by batch ID followed by re-import from clean source34.

Cutover sequencing: (1) source goes read-only and team is notified; (2) final delta export captures everything that changed during the sandbox-test window; (3) delta upsert via Data Loader using Legacy_ID External IDs; (4) reconciliation queries run; (5) Validation Rules and Triggers re-enabled with regression test pass; (6) users get login access and a 48-hour hyper-care window; (7) source decommission scheduled 30 to 90 days out, never same day.

Migration partners and tools

Summit and Crest Salesforce Partners, iPaaS vendors, specialist migration shops — what each is good for and how to choose.

The Salesforce Partner Program tiers consulting firms by Navigator certifications, Customer Satisfaction (CSAT) scores and Salesforce-credentialed engineer count. The named tiers are Global Strategic, Summit, Summit+, Crest and Ridge. 70 percent of Salesforce implementations are delivered through Partners rather than direct, and most non-trivial migrations end up with one.

Deloitte Digital, Accenture, Capgemini, IBM and Slalom dominate the global Strategic tier for enterprise multi-cloud rollouts. For mid-market Sales Cloud migration projects specifically, Summit-tier partners with explicit competitor-exit practices (Salesforce-from-HubSpot, Salesforce-from-Pipedrive, Salesforce-from-Microsoft Dynamics) tend to ship cleaner than generalist implementation shops. Salesforce also runs Professional Services in-house — typically the most expensive option but the one with deepest product-team access.

On the ETL and iPaaS side, MuleSoft (Salesforce-owned) is the default for enterprise integration with on-prem source systems, Informatica Cloud is common in regulated industries, and Fivetran, Airbyte, Stitch and Workato cover the warehouse-first stack. Their role in a migration is rarely the migration itself — it is the staging layer that lands source data, the transformation layer that converts picklist values and resolves OwnerIds, and the ongoing-sync layer that takes over once the one-time migration completes.

Dataloader.io and Skyvia sit in the lighter tier, useful for one-shot loader runs without writing code. Cloudingo and DemandTools handle the dedup-and-cleanse pass before insert.

Managed-migration cost ranges vary widely. A clean Pipedrive- or HubSpot-to-Salesforce move of under 25,000 records, standard objects only, no historical activities, typically lands in the $20,000–$60,000 range depending on data volume and the business-process re-mapping required. A multi-org consolidation with deal history, Custom Objects, OpportunityLineItem reconstruction and Apex/Flow rebuild runs $60,000–$500,000+, driven by record count, custom-field complexity, and integrations that need rebuilding13.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Salesforce migrations and handles the External ID schema design, async loader orchestration, Validation Rule and Trigger bypass setup, restricted-picklist transformation, historical-data preservation, and the reconciliation work described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on record count and source platform, with separate line items for Custom Objects, Apex/Flow rebuild scope and historical activity depth so the scope is transparent before signature.

This is one of several legitimate paths — the right choice for any given team depends on whether they want a Summit Partner with a wider services footprint, Salesforce Professional Services with deepest product-team access, an iPaaS-first approach via MuleSoft, or a specialist migration vendor focused on the load itself. [Explore FlitStack →](/contact)

Salesforce migration checklist

An eight-phase, task-by-task punch list for moving Accounts, Contacts, Leads, Opportunities, and historical activity into Salesforce Sales Cloud. Typical timeline: 6–16 weeks.

0. Decide & Plan9 tasks
  • Define migration scope by Salesforce object. Document explicitly which standard objects are in scope (Account, Contact, Lead, Opportunity, OpportunityLineItem, Product2, Pricebook2, Campaign, CampaignMember, Task, Event, Note, ContentVersion) and which custom objects from the source map to which destination object.If skipped: Scope ambiguity surfaces mid-cutover as missing objects, forcing emergency re-imports against governor limits.
  • Define historical-data scope and cut-off date. Decide how many years of closed Opportunities, completed Tasks, Events, and Notes move over. Decide whether email and call logs are in or out. Decide whether attachments / ContentVersion files are in or out.If skipped: An unbounded historical scope inflates storage, breaks the cutover window, and bumps into File Storage and Data Storage limits.
  • Identify the Salesforce edition and storage profile. Confirm Enterprise (500 custom fields per object) vs. Unlimited (800), and check current Data Storage and File Storage allocations against projected post-migration usage.If skipped: Hitting storage caps mid-load aborts bulk loads and forces a paid storage add-on at short notice.
  • Document legal and residency constraints. Confirm whether the org must run on Hyperforce in an EU region for GDPR, capture SOC2/HIPAA evidence requirements, and document any data-retention policies that change at cutover.If skipped: EU residency violations after go-live require a Hyperforce region migration that is far more expensive than placing the org correctly up front.
  • Assign a single accountable DRI and a stakeholder map. Name one decision-maker for scope changes, plus a RACI covering Sales Ops, Sales Leadership, RevOps, IT, Security, and Legal.
  • Define written success criteria. Specify the exact conditions that must hold before sign-off: record-count parity per object, aggregate pipeline value match within X%, sample-record field-by-field accuracy at Y%, and zero open critical UAT defects.If skipped: Without falsifiable criteria, the sponsor declares the project done while critical data gaps persist.
  • Set the cutover window and source-system freeze date. Pick a specific date and time, the freeze hour for source-system writes, and the planned read-only date for the legacy system.
  • Document out-of-scope items explicitly. List the data, automations, and integrations that will not move, so they are not raised as defects later.
  • Estimate load volume and storage consumption against the cutover window. Multiply expected record volume by Data Loader batch behavior, factor in test runs and re-loads, and confirm the org fits within its 24-hour load budget and 15,000 daily batch cap.If skipped: Cumulative load volume from sandbox tests plus reloads can hit ceilings hours before cutover finishes.
1. Pre-Migration Prep21 tasks
  • Export baseline record counts per source object. Capture counts for every object in scope (Accounts, Contacts, Leads, Opportunities, Activities, Notes, Attachments). This becomes the reconciliation reference for Phase 6.If skipped: Without a baseline, you cannot prove anything was lost.
  • Run dedup on source Contacts using email as the match key. Resolve all duplicate Contacts before export. Document which surviving record wins on conflict.If skipped: Duplicates landing in Salesforce trigger Duplicate Rule blocks mid-load and break downstream email-based upserts.
  • Run dedup on source Accounts using normalized company name + domain. Resolve company-level duplicates and reparent child Contacts and Opportunities to the surviving Account.If skipped: Duplicate parent Accounts split pipeline reporting and break sales-team rollups after cutover.
  • Standardize email casing, phone formats, and ISO country codes on source records. Lowercase emails, convert phone numbers to E.164, and map country names to ISO-3166-1 alpha-2.If skipped: Picklist Validation Rules on Country reject non-ISO values, blocking row-level inserts.
  • Resolve source records missing fields that are required on the Salesforce side. Account.Name, Contact.LastName, Lead.Company, Lead.LastName, and Opportunity.Name + StageName + CloseDate are required on insert.If skipped: Missing required fields fail per row and pollute error logs with thousands of rejections.
  • Identify orphaned activities, notes, and attachments in the source. Flag records whose parent will not be migrated so they are dropped or re-parented before export.
  • Provision the production Salesforce org and at least one Full or Partial Copy Sandbox. A Full sandbox refreshes from production data; a Partial Copy includes a sampled subset. Developer sandboxes hold metadata only and are insufficient for volume testing.If skipped: Testing volume in a Developer sandbox understates throughput and lets governor-limit and storage issues surface in production.
  • Configure org-level settings: currency, fiscal year, locale, timezone, Multi-Currency. These flags affect how the import parser interprets dates, decimals, and currency values and cannot be changed silently after data lands.If skipped: Toggling Multi-Currency or fiscal year after data lands corrupts historical Opportunity amounts and forecast rollups.
  • Create users in advance with the correct Profiles, Roles, and Permission Sets. Owner IDs on imported records must already exist. Use Permission Sets for granular access rather than cloning Profiles per user.If skipped: Loads fail at row level when OwnerId references a user that was not created or is deactivated.
  • Grant the migration user the 'Set Audit Fields upon Record Creation' permission. Without this permission, the platform overwrites CreatedDate and CreatedById with the load timestamp and the migration user.If skipped: Historical CreatedDate values are silently replaced and cannot be re-applied after the fact.
  • Create all custom objects, custom fields, and field-level security ahead of import. Importing into a field that does not exist silently drops the data. Enterprise allows 500 custom fields per object; Unlimited allows 800.If skipped: Missed custom fields cause silent data loss with no per-row error.
  • Restrict picklist values to the canonical set that will receive imported data. On any restricted picklist, bulk loads reject values that are not in the defined value set; pre-load the entire source domain into the picklist or expand the set before import.If skipped: Restricted picklist ENUM rejections cancel entire batches with cryptic STRING_TOO_LONG-style errors.
  • Mark one custom field as External ID on every object you plan to upsert into. Create a unique, indexed External ID field per object (for example Account.LegacyId__c) so upserts can match by source primary key. Up to 25 External ID fields are allowed per object.If skipped: Without an External ID, retries duplicate every record, and parent/child relationships cannot be wired up by source ID.
  • Build Record Types, Page Layouts, and a Sales Process per Opportunity stage flow. Each Record Type maps to one Sales Process, which controls which Opportunity StageName values are valid for records of that type.If skipped: Opportunities load with stages not allowed by their assigned Sales Process, leaving records in invalid states.
  • Deactivate or temporarily soften Validation Rules, Workflow Rules, Flows, and Apex Triggers on insert. Validation Rules and Triggers fire on every bulk insert. Insert a bypass condition keyed off a custom checkbox or the migration user to skip them during load.If skipped: Active rules can reject 100% of rows or fire side-effect emails to thousands of customers.
  • Confirm Master-Detail vs. Lookup vs. Junction Object decisions for every custom relationship. Master-Detail cascades delete and locks ownership to the parent. Junction Objects use two Master-Detail fields. Convert source many-to-many relationships into Junction Objects before mapping.If skipped: Choosing Master-Detail late forces re-creating fields and re-loading children because Master-Detail cannot be changed to Lookup after data lands.
  • Pause every integration on the destination side until cutover completes. Disable Marketing Cloud sync, calendar sync, Slack notifications, and external system Outbound Messages so test loads do not spam customers or partners.If skipped: An active integration during sandbox or production load broadcasts thousands of false notifications.
  • Configure Duplicate Rules and Matching Rules in 'Report only' mode for the load window. Set rules to log duplicates without blocking. Re-enable blocking mode after Phase 6 reconciliation.If skipped: Blocking Duplicate Rules reject legitimate records during multi-batch loads of the same parent.
  • Communicate the freeze window to all source-system users. Send the exact freeze timestamp, the read-only date, and the destination go-live time at least two weeks in advance.
  • Schedule role-based Salesforce training for sales reps, managers, and admins. Cover Lightning navigation, Kanban opportunity boards, reports, and how to log activities.
  • Designate first-responder admins for the first 72 hours after cutover. Name primary, secondary, and escalation contacts and publish a triage SLA.If skipped: Without a triage roster, user-reported defects sit unowned and erode trust in the new platform.
2. Source Export13 tasks
  • Export Accounts with every standard and custom field as UTF-8 CSV. Include the source primary key column so it can populate Account.LegacyId__c as External ID.If skipped: Missing the source primary key forces fuzzy matching downstream and reintroduces duplicates.
  • Export Contacts with every standard and custom field as UTF-8 CSV. Include the source Account-FK column so the loader can wire Contact.AccountId via External ID.
  • Export Leads with every standard and custom field as UTF-8 CSV. Capture Lead.Status, Lead.Source, conversion flag, and any custom score fields.
  • Export Opportunities with every standard and custom field as UTF-8 CSV. Include StageName, CloseDate, Amount, OwnerId-equivalent, AccountId-equivalent, source primary key, and the historical CreatedDate.If skipped: Missing CloseDate or Amount blocks Opportunity load because both are required on insert.
  • Export Opportunity-Product line items as a separate CSV. Capture quantity, unit price, discount, and parent-opportunity source key per line.
  • Export Tasks and Events to separate CSVs. Salesforce stores closed Tasks/Events in an archive after a year and IsArchived cannot be edited after the fact. Plan migration order accordingly.If skipped: Archived activities in the destination cannot be patched after the fact; capture all needed fields on the first load.
  • Export Notes and ContentNotes content as a separate CSV. Confirm whether source notes preserve line breaks and HTML formatting; document the encoding.If skipped: Line breaks and special characters lost in export cannot be reconstructed.
  • Export ContentVersion / Attachment binaries plus a metadata sidecar. The sidecar maps each file to its parent record source key and captures original filename, file size, and upload timestamp.
  • Export Campaigns and CampaignMember junctions. Capture member status, response date, and parent Campaign source key.
  • Export the user list with role hierarchy and Profile assignments. Capture email, alias, ProfileName, RoleName, manager, and active status so Salesforce users can be mapped to source owners.
  • Export pipeline / stage definitions and any custom workflow states. These become the source side of the picklist mapping in Phase 3.
  • Capture screenshots and exports of source automations, reports, and dashboards. These do not transfer; the screenshots seed the rebuild list in Phase 7.
  • Record the exact UTC timestamp of every export. This defines the delta window for the Phase 5 final pull.If skipped: Without timestamps, the delta cannot be computed and last-minute source edits are lost.
3. Transform & Map23 tasks
  • Build a master field-mapping spreadsheet covering every source field. For each row capture: source field, destination object, destination field name, destination data type, transformation rule, required-on-insert flag, picklist constraint, and disposition (load / drop / concat to Description).If skipped: Undocumented mappings cause silent drops and unreproducible loads.
  • Choose the upsert key per object and document it. Standard practice: External ID on every custom and standard object (Account.LegacyId__c, Contact.LegacyId__c, Opportunity.LegacyId__c). Avoid email as the sole Contact key because emails change.If skipped: Using a mutable column as upsert key creates duplicates on every re-run.
  • Resolve every picklist value mismatch between source and destination. List source values, list destination Sales Process-allowed values, and map every source value to exactly one destination value or to a documented 'Other' bucket.If skipped: Unmapped picklist values trigger ENUM rejection on restricted picklists.
  • Decide handling for source fields with no destination equivalent. Options: drop, concat into Description, or create a new custom field. Document one decision per field.
  • Map source owner IDs to Salesforce User IDs. Use a bridging CSV that joins source-owner email to Salesforce User.Username; for orphaned owners assign to a single 'Data Migration' user.If skipped: Unmapped owners default to the migration user and break territory and assignment-rule logic.
  • Convert all date and datetime values to ISO-8601 with explicit timezone. Salesforce expects YYYY-MM-DDThh:mm:ss.000+0000 for datetimes and YYYY-MM-DD for dates. Localize via the org timezone confirmed in Phase 1.If skipped: Mismatched timezones shift CloseDate by a day and trip up fiscal-period reporting.
  • Normalize currency values to plain decimals with a period separator. Remove thousands separators, currency symbols, and trailing whitespace. For Multi-Currency orgs, populate CurrencyIsoCode per row.
  • Truncate or split source fields that exceed Salesforce character limits. Account.Name is 255, Contact.LastName is 80, standard Description is 32k. Build a truncation log so over-length values are preserved in a sidecar.If skipped: Silent truncation removes legal company suffixes and breaks downstream matching.
  • Re-encode every CSV as UTF-8 without BOM. European spreadsheet exports default to UTF-8 with BOM or to UTF-16. Data Loader parses UTF-8 without BOM.If skipped: BOM headers turn the first column name into garbage and break field mapping on the first row.
  • Escape commas, quotes, and newlines inside text fields. Wrap values in double quotes; escape inner double quotes by doubling them. Test with a sample that contains all three.If skipped: Unescaped newlines split one logical row into two, misaligning every subsequent column.
  • Validate that every record has a non-null value in every required field. Run a column-by-column null check against the required-field list compiled in Phase 1b.
  • Decide and implement the strategy for original CreatedDate. With 'Set Audit Fields upon Record Creation' enabled, populate the CreatedDate column at load. Otherwise add a Custom__c 'Original Created Date' field and populate it from the source.If skipped: Losing the original CreatedDate breaks aging reports, time-to-close metrics, and historical Activity ordering.
  • Decide and implement the strategy for record ownership at load time. Choose: best-match by email to existing User, fallback to a single 'Data Migration' user, or hold ownership transfers until UAT sign-off.
  • Decide and implement the strategy for ContentVersion attachments. Either re-upload binaries as ContentVersion records, or store as external links in a custom URL field. Re-upload preserves search; external links save File Storage.If skipped: Re-uploading without staging the binaries first exhausts File Storage and stalls the load.
  • Pre-build the load-order dependency graph. Users first → Accounts → Contacts → Leads → Campaigns → Opportunities → OpportunityLineItem → Tasks/Events → Notes → ContentVersion. Junction Objects load after both parents exist.If skipped: Loading children before parents leaves dangling foreign keys and forces a full re-run.
  • Map source pipeline stages to Opportunity StageName values, one per Record Type. If the source has multiple pipelines, model each as a separate Record Type + Sales Process + Page Layout. Stage values not in the assigned Sales Process will be rejected.If skipped: Cross-pipeline stage values cause silent assignment to the default Record Type and break funnel reporting.
  • Compute and stamp Opportunity.IsClosed and IsWon from the source stage definition. Salesforce derives these from the Sales Process definition, not from the input value; confirm the StageName already implies the expected closed/won semantics in the destination.
  • Decide handling for Opportunity.CloseDate on already-closed historical deals. Preserve original close date even if it predates the current fiscal year; do not re-stamp to migration day.If skipped: Re-stamping CloseDate spikes the current period's reported revenue and corrupts forecast accuracy.
  • Re-derive Lead score and grade in the destination, not in the source export. Lead-scoring formulas, Einstein Lead Scoring inputs, and Marketing Cloud Account Engagement grades are platform-computed. Capture the raw inputs and let the destination recompute.If skipped: Carrying over stale numeric scores collides with the destination's scoring model and confuses sales reps.
  • Map source 'won/closed-lost' reasons to a Salesforce picklist on Opportunity. Either a standard Loss Reason or a custom picklist; confirm the value set is restricted and pre-loaded with every source value.
  • Decide handling for Lead conversion lineage. Source converted leads typically map to a Contact + Account + Opportunity triad already; either skip Lead import for converted records or load them as Leads with IsConverted=true and ConvertedAccountId / ConvertedContactId set via External ID.If skipped: Loading converted leads as open Leads pollutes the Lead queue and double-counts pipeline.
  • Translate source contact roles to OpportunityContactRole records. Export the junction separately and load after Opportunity + Contact both exist; set IsPrimary=true on exactly one row per Opportunity.
  • Reconstruct Activity timeline ordering before load. Sort by source ActivityDate and CreatedDate so Activities appear in chronological order on the destination timeline view.
4. Sandbox Test Migration13 tasks
  • Refresh the Full or Partial Copy Sandbox immediately before the test run. A stale sandbox lacks the latest metadata changes from Phase 1b and will not reflect production load behavior.If skipped: Testing against stale metadata hides field-level-security and Validation Rule defects.
  • Load a 1–5% representative sample of each object via Data Loader. Data Loader auto-chunks into batches; use Workbench for ad-hoc small loads.
  • Spot-check 10 random sandbox records per object field-by-field against source. Verify standard fields, custom fields, picklist values, and number/date formats.If skipped: Sampling fewer than 10 misses encoding and transformation bugs that affect 1% of rows.
  • Specifically test long strings, special characters, NULL, and Unicode emoji. Load a fixture row that exercises maximum-length values, embedded quotes, embedded newlines, leading/trailing whitespace, NULL, and 4-byte UTF-8 characters.If skipped: Unicode astral characters silently truncate at the database layer and corrupt names.
  • Test relationship preservation via External ID lookups. Confirm Contact.AccountId, Opportunity.AccountId, OpportunityLineItem.OpportunityId, and Task.WhatId all wire to the correct parent record.If skipped: Lookup-by-external-ID failures point children at the wrong parent and corrupt the whole hierarchy.
  • Confirm the 'Set Audit Fields' strategy actually preserved CreatedDate. Inspect a sample of sandbox records via SOQL to verify CreatedDate matches the source timestamp, not the load timestamp.
  • Run a Validation Rule and Apex Trigger fire-pattern audit during the test load. Use the Bulk Data Load Jobs setup page to confirm rules fired or were bypassed as designed; review any per-row errors emitted by Triggers.If skipped: A Trigger firing on insert can exceed the 150 DML statement governor limit and abort a batch partway.
  • Test ContentVersion / file-attachment upload at sample scale. Confirm files arrive, parent-record links resolve, and File Storage consumption per record matches the projection from Phase 0.
  • Run a full-volume rehearsal in the Full sandbox. Load every record at production volume. Time each step end-to-end.If skipped: Skipping volume rehearsal hides bulk throttling and 24-hour load budget consumption that only appears at full scale.
  • Extrapolate sandbox timing to the production window. Multiply by 1.5x for safety margin. If the projection exceeds the cutover window, re-plan before Phase 5.
  • Have 2–3 sales-ops domain experts spot-check the sandbox data. Pick known accounts and open opportunities; ask the expert whether everything looks right at the record level.
  • Document every defect with the failing row, the rule that rejected it, and the fix. Maintain a defect ledger; close each defect before sign-off.
  • Obtain written sandbox sign-off before scheduling production cutover. Sponsor + sales-ops lead must sign.If skipped: Proceeding to production without sign-off transfers all sandbox defects into the live org.
5. Production Cutover12 tasks
  • Confirm the source-system freeze is in effect. Query source audit logs to verify no writes in the last 60 minutes before pulling the final export.If skipped: Writes after the freeze produce a silent delta that never reaches the destination.
  • Pull the final source export with timestamps. Capture the delta from the Phase 2 baseline plus any rows whose source CreatedDate or LastModifiedDate falls in the gap window.
  • Disable Workflow Rules, Process Builder flows, Flows, and any active Triggers on insert. Either deactivate at the rule level or route every load through the bypass-condition pattern created in Phase 1b.If skipped: Active automation fires emails, posts to Slack, and creates downstream records during the load, multiplying side effects by the row count.
  • Disable Duplicate Rule blocking; leave matching in 'Report' mode. Re-enable blocking after Phase 6 reconciliation finishes.
  • Load Users first, then Accounts, then Contacts and Leads. Use Data Loader upsert keyed on the External ID field per object so reruns are idempotent.If skipped: Loading Contacts before their parent Accounts orphans the children and forces a delete-and-reload.
  • Load Campaigns, Opportunities, OpportunityLineItems, OpportunityContactRole, and Junction Objects in that order. Children must reference parents by External ID — never by Salesforce Id, which does not exist until the parent insert completes.
  • Load Tasks, Events, Notes, and ContentVersion last. These reference WhatId / WhoId on already-loaded parents and consume the most File Storage.
  • Capture Data Loader job IDs, row counts, and error files for every load step. Persist these to a runbook log; they are evidence for audit and the basis for Phase 6 reconciliation.If skipped: Without job IDs, error rows cannot be retrieved from the Bulk Data Load Jobs page after the retention window expires.
  • Cross-check destination row count vs. source row count after every load. Variance above 0 must be investigated before moving to the next object.If skipped: Continuing past a variance compounds errors and makes root-cause analysis impossible.
  • On any partial failure, stop and diagnose before re-running. Idempotent External ID upserts let you fix the transform and re-run the same file without duplicates.
  • Re-enable Validation Rules, Triggers, Workflow Rules, and Duplicate Rule blocking. Verify each is back to its production state before opening the org to users.
  • Run a smoke test as 3 representative user Profiles. Log in as a Sales Rep, a Sales Manager, and an Admin; confirm record visibility, list views, and Sharing Rules behave as designed.
6. Validate18 tasks
  • Compare per-object record counts: source vs. Salesforce. Run SOQL count queries against Account, Contact, Lead, Opportunity, OpportunityLineItem, Task, Event, Note, ContentVersion, CampaignMember. Investigate any non-zero delta.If skipped: Even a single-record gap can mask a Validation Rule that quietly dropped a class of rows.
  • Compare total open-pipeline value: source vs. SUM(Opportunity.Amount) where IsClosed=false. Tolerance should be zero in single-currency orgs and within the FX rate-table tolerance in Multi-Currency orgs.If skipped: Pipeline drift erodes sales-leader trust on day one of go-live.
  • Compare closed-won revenue: source vs. SUM(Opportunity.Amount) where IsWon=true. Reconcile by fiscal period to catch CloseDate timezone shifts.
  • Spot-check 25–50 randomly selected records field-by-field across source and destination. Stratify the sample by object and Record Type so every Sales Process is represented.
  • Verify all custom field values on a sample of 50 records per object. Check both the value and the field's history-tracking entry where Field History Tracking is enabled.
  • Verify Contact-to-Account parent relationships on a sample of 100 Contacts. Query Contact.AccountId.Name and confirm it matches the source.If skipped: External ID lookup misses leave Contacts on the wrong Account, breaking territory routing.
  • Verify Opportunity-to-Account and Opportunity-to-OpportunityLineItem linkages. Confirm OpportunityLineItem rollups (Amount, Quantity) match Opportunity totals.
  • Verify Task and Event parent links via WhatId and WhoId. Activities should appear in the Related list on the parent Account / Contact / Opportunity timeline.
  • Verify Junction Object rows resolve to both parents. Sample 25 OpportunityContactRole and any custom junction rows.
  • Verify ContentVersion files are accessible and linked to the right records. Open 10 sample files from the Files Related list per parent object type.If skipped: Broken file links surface as user-reported defects in week one and are expensive to retro-fix at scale.
  • Confirm original CreatedDate is preserved on a 50-record sample. Query Account.CreatedDate via SOQL and compare to the source. If the strategy used a custom field instead, confirm the custom field populated correctly.
  • Run a GDPR data-residency audit against the Hyperforce region setting. Confirm the org's instance is in the expected EU region for any EU-resident personal data; verify backup region matches.If skipped: Residency violations discovered later require a Hyperforce region migration and DPA renegotiation.
  • Capture Setup Audit Trail and Login History snapshots for the cutover window. Export both to long-term storage as SOC2 / compliance evidence.
  • Confirm Field History Tracking is enabled on the agreed list of fields. Standard Field History Tracking retains 18 months and tracks 20 fields per object; document any gaps against the compliance requirement.
  • Run UAT with 3–5 power users from sales, sales ops, and management. Provide a scripted workflow covering log a call, update an Opportunity stage, convert a Lead, and run a Forecast.If skipped: Skipping UAT defers defect discovery to end users on day one when the support load is already peaked.
  • Document every UAT defect with severity and ownership. Triage critical defects before sign-off; defer cosmetic defects to Phase 7.
  • Have UAT users sign off in writing. Capture sign-off in the same defect ledger used in Phase 4.
  • Obtain written sign-off from the migration sponsor before Phase 7. Sponsor must confirm: counts reconcile, sample-record accuracy meets the Phase 0 criteria, UAT critical defects are closed.If skipped: Skipping formal sign-off leaves scope-of-completion ambiguous and reopens the project months later.
7. Post-Migration Cleanup12 tasks
  • Announce go-live to all end users with login URL and the first-responder contact. Include a one-page quick-start covering Lightning navigation and the locations of common reports.
  • Run role-segmented training sessions for reps, managers, and admins. Cover the Opportunity Kanban, mobile app, Einstein insights where licensed, and how to log activities.
  • Set the source system to read-only on the announced date. Block writes but keep reads available for the documented retention period.If skipped: Leaving the source writable encourages reps to keep working in the old system, fracturing the source of truth.
  • Rebuild reports and dashboards in Salesforce. Reports do not transfer; use the Phase 2 screenshots as a build list. Prioritize the 10 most-used reports first.
  • Rebuild automations: Flows, Process Builder flows, Workflow Rules, and Approval Processes. These do not transfer; reconstruct from the Phase 2 capture. Test each one against migrated records before activation.If skipped: Activating untested Flows on top of migrated data can mass-update or mass-email customers.
  • Re-establish integrations: calendar sync, email sync, Marketing Cloud, Slack, BI tools. Re-authenticate, point at production, and run a smoke test per integration.
  • Re-enable Duplicate Rules in blocking mode. Confirm matching keys still resolve to a single record per entity and that the Duplicate Job report runs clean.
  • Configure Sharing Rules, Role Hierarchy, and Permission Set assignments per role. Confirm record visibility for each Profile against the agreed access matrix.If skipped: Over-permissive Sharing Rules expose pipeline data to the wrong territory; under-permissive rules block reps from their own records.
  • Schedule a 30-day post-migration retrospective with the project team. Capture what went well, what surprised the team, and what to change for the next migration.
  • Document the source-system decommission date. Typically 90 days after cutover, after the final retention window. Confirm with Legal and Finance.
  • Archive source-system exports and Data Loader job logs to long-term storage. Encrypt at rest, restrict access, and document retention per the policies captured in Phase 0.If skipped: Without retained exports, a forensic question six months in cannot be answered.
  • Close the migration project formally with a final status report. Include: tasks completed, deferred items, final defect count, sign-off list, and a recommended day-30 checklist for the operations team.

Questions, answered

Migrating to Salesforce: questions

How long does migration to Salesforce take?

A clean legacy-CRM migration of under 25,000 records on standard objects runs one to two weeks end-to-end. A multi-org consolidation with Apex/Flow rebuild, historical activities, OpportunityLineItem reconstruction and integration rebuilds runs four to twelve weeks of elapsed time including sandbox dry-runs, validation, training and a 48-hour hyper-care window.

Can I migrate from HubSpot to Salesforce?

Yes — HubSpot is a common Sales Cloud migration source when teams hit HubSpot's contact-tier pricing wall. Object models align cleanly (Contacts, Companies, Deals map to Contact, Account, Opportunity), but HubSpot Workflows, Sequences and HubSpot Score do not transfer and must be rebuilt as Salesforce Flows and Einstein Lead Scoring.

Can I migrate from Pipedrive to Salesforce?

Yes. Pipedrive's Persons, Organizations and Deals map cleanly to Contact, Account and Opportunity, and historical Activities map to Task and Event with backdated ActivityDate. Plan for picklist value alignment, Pipedrive owner-email to Salesforce User mapping, and rebuilding Pipedrive workflows as Salesforce Flows or Validation Rules from scratch.

Does Salesforce preserve original CreatedDate on import?

Only if you file a support case requesting the org-wide Create Audit Fields permission before the migration. With it enabled, CreatedDate, CreatedById, LastModifiedDate and LastModifiedById can be set explicitly during insert. Without it, every imported record is stamped to load day — preserve original timestamps in custom Legacy_Created_Date__c fields instead.

What's the difference between Data Import Wizard and Data Loader?

Data Import Wizard is the UI tool — capped at 50,000 records per import on a limited object set (Leads, Accounts, Contacts, Campaign Members, Solutions, Person Accounts and Custom Objects) and not Opportunities, Cases or Products. Data Loader is the desktop client supporting every Standard and Custom Object, including async high-volume loads.

Can I migrate Custom Objects to Salesforce?

Yes. Custom Object schema must be deployed to the destination org via a deployment tool before any records load. Custom Objects use the same External ID upsert mechanism, the same field cap (500 Enterprise / 800 Unlimited), and the same Master-Detail / Lookup relationship rules.

What happens to Opportunity stage history during migration?

OpportunityHistory is read-only — you cannot insert historical stage transitions directly. Recreate every Sales Process and StageName value per Record Type before import, then populate custom datetime fields like Stage_Entered_Qualification__c from the source to preserve the timeline. Einstein Forecasting and stage-conversion reports rebuild from the migrated current state forward.

Is there an undo or rollback for Salesforce imports?

Partially. The Recycle Bin holds deleted records for 15 days. Setup → Undo an Import undoes Data Import Wizard imports launched within 24 hours. Data Loader has no native undo — practitioners stamp every imported row with an Import_Batch_ID__c custom field for SOQL-based bulk-delete and re-import.

Get a quote

Moving to Salesforce?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Salesforce setup with you, then send a quote.

Get a quote