# Move from Salesforce to 121 CRM | Migration guide > Plan a careful move from Salesforce to 121 CRM using documented exports, field mapping, sample testing, reconciliation and clear migration limits. A useful decision about moving from Salesforce begins with the real data flow, not a logo on an integrations page. This Salesforce guide explains the documented method, practical setup or migration sequence, important limits and the acceptance checks a small business should complete before relying on it. ## A migration plan you can inspect Fictional example using Alder & Field; supplier capability is documented, while account availability and 121 service scope still need agreement for each customer. ## Capabilities explained ### Import and export Moves supported records through structured files, with mapping and validation needed before relying on the result. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Supports controlled migration and operational extracts when the data is prepared and reconciled. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. Bulk migration requires mapping and reconciliation; do not treat a completed import as proof of accuracy or reversibility. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Custom fields Adds structured fields to supported record types so a business can capture information it actually needs. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Replaces important notes and spreadsheet columns with searchable, reusable data. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Duplicate management Uses account rules and review steps to reduce or resolve repeated contact records. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Keeps teams from following up with the same person through conflicting records. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Contacts Stores a person or lead with contact details, activity, ownership and related records. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Gives a team one place to understand who a customer is and what has happened. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Opportunities Represents a potential sale or deal linked to a contact, value, owner and pipeline position. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Shows which customer conversations are active commercial work rather than general contacts. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ## What can leave Salesforce, and in what form The provider documentation reviewed on 11 October 2026 describes this route: Use Salesforce Data Export or object-level exports, then reshape selected records into destination CSV files. Treat the Salesforce method as a starting boundary, because permissions, editions and configured options can change the actual result. ### What the current documentation supports Accounts, contacts and opportunities can be exported as separate objects. For Salesforce, this is a general supplier capability; it does not confirm availability or inclusion in a particular 121 customer account. ### Another supported part of the documented scope Salesforce can include files in a wider backup export when the administrator selects them. For Salesforce, this is a general supplier capability; it does not confirm availability or inclusion in a particular 121 customer account. ### A practical business question Which active customer relationships must remain useful after the move, and what source history is genuinely needed to support them? Answer that before asking for every available field. ## A controlled way to move from Salesforce Use a bounded, reversible Salesforce test before any live change; this sequence is practical guidance, not a promise that 121 has access to either account or that every step is included in a 121 package. ### 1. Preserve the source Keep an untouched source export and record when, by whom and under which permissions it was created. For Salesforce, use the documented route rather than copying an on-screen view and assuming it is complete; apply that check to the documented Salesforce route. ### 2. Map records and meaning Map contacts, organisations, opportunities, owners, stages, consent and important dates separately. Give every source field a destination, transformation rule or deliberate exclusion; apply that check to the documented Salesforce route. ### 3. Test an awkward sample Use ordinary records alongside duplicates, missing identifiers, long text, unusual characters and linked opportunities. Import contacts before dependent opportunities and keep the test isolated from live messaging; apply that check to the documented Salesforce route. ### 4. Reconcile before cutover Compare source and destination counts, inspect relationships and exceptions, obtain user acceptance and define a stop or rollback decision before the live move; apply that check to the documented Salesforce route. ## How Alder & Field could test the decision Alder & Field is a property-maintenance business. Its fictional Salesforce records and narrow acceptance test demonstrate the method without implying a live connection or customer result. ### The operating need The team needs current customers and open work to remain visible after leaving Salesforce; it does not need to recreate every historical screen or automation. ### The trial Alder & Field exports a bounded set of current contacts and open work from Salesforce. The team maps five required customer fields and one pipeline, imports twenty records, then reconciles the count, owners, stages and a sample of notes before deciding whether to continue. ### The evidence Alder & Field's reviewer keeps the Salesforce source count, test input, mapped output, timestamps, owner, exception log and configured-permission evidence; a pass means this agreed scenario behaved as expected, not that every future scenario is guaranteed. ### The decision Alder & Field names an owner to accept, revise or reject the Salesforce design; anything unexplained remains outside live use until it has a documented rule, monitoring route and human response. ## What to check before relying on Salesforce Salesforce documentation establishes general capability, not customer-specific availability, commercial inclusion or a 121 migration commitment; put those boundaries in the decision rather than small print after go-live. ### What the connection or export does not solve Object relationships, activities, automation and configuration do not become equivalent destination records automatically. ### A second boundary to plan around The source edition, permissions and custom data model determine what the administrator can export. ### Account and commercial boundary Confirm the relevant HighLevel, Salesforce and connector plans, permissions, usage charges and supplier terms in the customer's own accounts. This Salesforce page does not claim that integration or migration work is included in the 121 subscription. ### Live acceptance still required Before live Salesforce use, confirm an owned connection, run a representative test, reconcile results and record failure handling; no live account test was performed for this public guide, so those checks remain customer-specific implementation work. ## Frequently asked questions ### Can every Salesforce record be moved automatically? No. The documented source export and HighLevel import cover particular objects and fields. Activities, relationships, files, automations, configuration and history often need separate extraction, transformation, rebuilding or deliberate exclusion. ### What should be tested before leaving Salesforce? Test a representative sample of contacts and open work, including duplicates, missing values, custom fields and linked opportunities. Reconcile counts and relationships, ask users to inspect the result and keep an agreed rollback or correction route. ### Will 121 move all of our Salesforce data as part of the subscription? This page does not make that commitment. Migration scope, source access, data quality, volume, history, connected systems, testing and responsibilities must be assessed and agreed separately before work begins. ### Should Salesforce be closed as soon as the first import succeeds? No. Keep a controlled source archive and a defined overlap or read-only period until reconciliation, user acceptance, communication checks and the cutover decision are complete. ## Related CRM pages - [/crm/switch](https://121.direct/crm/switch) - [/crm/guides/crm-migration-checklist](https://121.direct/crm/guides/crm-migration-checklist) - [/crm/templates/field-mapping](https://121.direct/crm/templates/field-mapping) - [/crm/switch/from-activecampaign](https://121.direct/crm/switch/from-activecampaign) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.