Skip to content
Get a quote

EspoCRM to Salesforce migration

We migrate Contacts, Accounts, Opportunities, Cases, and Custom Entities from EspoCRM into Salesforce with EspoCRM's 200-record API ceiling handled through chunked pagination, custom entity dependency chains resolved via topological sort, and filesystem-stored attachment files transferred alongside the database export before cutover.

Short answer

FlitStack AI migrates contacts, accounts, leads, contact + accounts and opportunities from EspoCRM 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.

By

Source EspoCRM
DestinationSalesforce
ContactAccountLeadContact + AccountOpportunity
Mapped field by field · sample run · one-click rollback

What moves from EspoCRM to Salesforce?

Moving from EspoCRM to Salesforce is a structural migration across different deployment models: EspoCRM's AGPLv3 open-source platform (self-hosted or cloud at $15-$69 per user per month) versus Salesforce's multi-tenant SaaS ecosystem (starting at $75 per user per month on Sales Cloud Starter).

Read the full summary

EspoCRM's Entity Manager lets administrators build custom entity types without code, and those custom entities carry cross-reference relationships that must be resolved in dependency order during migration. We handle the 200-record API ceiling through paginated extraction, transfer filesystem-stored attachment files from self-hosted instances separately from the database export, and map EspoCRM's Leads, Contacts, Accounts, Opportunities, Cases, and Campaigns to their Salesforce equivalents. Salesforce Validation Rules and field-level security profiles can block record inserts if not coordinated with the destination org admin before migration. Workflows, BPM processes built with EspoCRM's Advanced Pack extension, and custom PHP/Before-Save scripts do not migrate; we deliver a written inventory for the customer's admin to rebuild in Salesforce Flow. Files stored on EspoCRM's filesystem require a separate transfer step that database exports alone do not capture.

1:1

Contact → Contact

EspoCRM Contact records map directly to Salesforce Contact.

How it maps

The Email field serves as the dedupe key during import. We map all standard fields (FirstName, LastName, Phone, MobilePhone, MailingAddress) plus any custom fields. EspoCRM multi-email fields (multiple email addresses on one contact) require splitting: the primary email maps to Email and additional addresses are stored in a custom Textarea field custom_email_secondary__c. Multi-enum fields (capped at 20 options in EspoCRM) map to Salesforce Multi-Select Picklist fields with no option count limit.

1:1

Account → Account

EspoCRM Account records map to Salesforce Account.

How it maps

We use the Account Name as the dedupe key. The industry sector, annual revenue, number of employees, website, and billing address fields map directly. Custom fields on EspoCRM Account map to custom fields on Salesforce Account (with __c suffix). Account must be created before Contact import so that AccountId Lookup is satisfied at insert time.

1:1

Lead → Lead

EspoCRM Lead records map to Salesforce Lead.

How it maps

EspoCRM stores Lead status in a status field with custom values; we map those values to Salesforce Lead Status picklist entries, creating new Status values in the destination org if the EspoCRM values do not already exist. Converted Leads (those that have been converted to Contact and Account in EspoCRM) are handled separately: we migrate the original Lead record and link it to the converted Contact via a custom field espo_converted_contact_id__c for audit trail.

1:N split

Lead conversion → Contact + Account (from conversion)

EspoCRM stores converted Lead records with links to the resulting Contact and Account.

How it maps

During migration, we identify converted Leads by the presence of convertedContactId and convertedAccountId fields, then create both the Account (if not already present) and the Contact in Salesforce, and store the original EspoCRM Lead ID on the Contact in a custom field espo_lead_id__c for lineage tracking.

1:1

Opportunity → Opportunity

EspoCRM Opportunity records map to Salesforce Opportunity.

How it maps

Stage, probability, amount, close date, and description fields migrate directly. The pipeline assignment in EspoCRM maps to a Salesforce Record Type and Sales Process that we configure before migration. Custom fields on EspoCRM Opportunity (including any fields tracking product lines or deal-specific attributes) map to custom Opportunity fields in Salesforce.

1:1

Case → Case

EspoCRM Case records (support tickets) map to Salesforce Case.

How it maps

Status, Priority, and Resolution fields map to their Salesforce equivalents. The conversation thread (case comments and customer replies) migrates as CaseComment records linked to the Case. Attachments on Cases are extracted from the EspoCRM filesystem (on self-hosted) or database (on cloud) and re-registered as Salesforce ContentDocument records linked to the Case via ContentDocumentLink.

What moves16 objects
EspoCRMSalesforce
  • ContactContact1:1
  • AccountAccount1:1
  • LeadLead1:1
  • Lead conversionContactsplit
  • OpportunityOpportunity1:1
  • CaseCase1:1

+ 10 more in the mapping below

How EspoCRM 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.

DimensionEspoCRMSalesforce
Deployment modelSelf-hosted (AGPLv3) or cloud-hosted; customer owns database and data filesMulti-tenant cloud-only SaaS; data stored on Salesforce infrastructure
Custom entity creationEntity Manager UI lets non-developers create custom types without codeCustom Objects require admin or developer access; __c suffix API naming convention
API record ceilingDefault 200 records per GET; maxSize parameter configurableBulk API 2.0 handles millions of records; REST API supports SOQL pagination
File attachmentsSelf-hosted stores files on server filesystem under data/files/Files migrate as ContentVersion records linked to ContentDocument
Workflow automationAdvanced Pack BPM and Workflow automation; no Salesforce equivalentSalesforce Flow (record-triggered, scheduled, screen) from Professional tier
Integration ecosystemLimited to Google Workspace, Outlook, Zoom, VoIP, StripeAppExchange with over 9,000 certified applications
Market share0.01% market share, ~34 known customers in CRM Platforms25.29% market share in CRM Platforms; dominant enterprise standard

What to watch for in a EspoCRM to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

EspoCRM 200-record API ceiling requires pagination strategy

EspoCRM's REST API returns a maximum of 200 records per GET request by default (controlled by the maxSize parameter).

How we handle it

Large datasets require paginated extraction loops that fetch sequential offset pages. We detect the total record count from the first response, configure maxSize explicitly to balance throughput against server load, and orchestrate chunked page fetches without silent truncation. Skipping this step results in only the first 200 records migrating regardless of total volume.

high

Custom entity cross-references require topological import ordering

EspoCRM Entity Manager custom entities that reference each other via link-multiple or foreign-key relationships create a chicken-and-egg problem during migration.

How we handle it

A custom Project entity linked to a custom Client entity cannot be imported if Client does not yet exist. EspoCRM enforces referential integrity on save, so records with missing parent references fail. We perform dependency graph analysis of all custom entity types during discovery, topologically sort the import order, and use ID remapping tables to resolve forward references when source IDs differ from target IDs.

high

Self-hosted filesystem attachment extraction is separate from database export

On self-hosted EspoCRM instances, uploaded files are stored on the server filesystem under the data/files/ directory rather than as blob records in the database.

How we handle it

A standard database export and restore captures the Attachment metadata records but not the actual file data. We identify Attachment records during discovery, extract the referenced files from the filesystem archive, and transfer them alongside the database migration, re-registering each file as a Salesforce ContentVersion record. Cloud-hosted EspoCRM instances store files in the database and migrate with the standard export.

medium

Salesforce Validation Rules block record inserts without coordination

Salesforce orgs commonly enforce Validation Rules (required field 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 destination Salesforce admin to grant the migration user Modify All Data and Bulk API permissions, and either temporarily disable Validation Rules during load or extend them with a migration-context bypass. Skipping this step results in 5-30 percent record rejection on first import attempt.

medium

Multi-enum field option cap of 20 in EspoCRM limits data fidelity

Multi-enum fields in EspoCRM are capped at 20 selectable options by default.

How we handle it

If your source EspoCRM data or destination mapping requires more than 20 options in a multi-select field, records may fail validation on import into Salesforce if the multi-select picklist is configured with a limited value set. We detect multi-enum fields during discovery, report option counts, and advise whether to use an unrestricted multi-select picklist in Salesforce or split into multiple fields before migration begins.

How the migration runs

  1. Discovery and source system audit

    We audit the EspoCRM instance across deployment type (self-hosted or cloud), API configuration, total record counts per entity type, custom entity types and their field definitions (exported from entityDefs metadata), active workflows and BPM processes (Advanced Pack), and attachment volume (file count and total storage size on filesystem for self-hosted).

    What this step covers

    We pair this with a review of the destination Salesforce org's current schema, Validation Rules, field-level security profiles, and available API licenses. The discovery output is a written migration scope with entity-level record counts, a custom entity dependency graph, and a Salesforce edition recommendation.

  2. Schema design and dependency resolution

    We design the destination Salesforce schema.

    What this step covers

    For custom entity types, we pre-create the custom objects with __c API names matched to EspoCRM entity names, including all custom fields, lookup relationships, and validation rules. We build the dependency graph for custom entities and define the topological import order. We configure Salesforce Record Types and Sales Processes for Opportunity migration. Schema is deployed into a Salesforce Sandbox first via metadata API for validation before production migration begins.

  3. Sandbox migration and reconciliation

    We run a full migration into a Salesforce Sandbox (Full Copy or Partial Copy) using production-like data volume.

    What this step covers

    The customer's EspoCRM admin and Salesforce admin jointly reconcile record counts, spot-check 25-50 records per entity type against the EspoCRM source, and validate that lookup relationships resolved correctly. Any mapping corrections, validation rule conflicts, or custom entity dependency issues surface here before production migration begins.

  4. Filesystem extraction and owner reconciliation

    For self-hosted EspoCRM instances, we extract all files from the data/files/ directory and index them against the Attachment records in the database.

    What this step covers

    For cloud-hosted instances, we extract file blob data from the database export. We also reconcile EspoCRM Users against Salesforce Users by email address match. Any EspoCRM User without a matching Salesforce User goes to a reconciliation queue for the customer's Salesforce admin to provision before record import resumes.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts first, then Contacts and Leads (with the Lead conversion split resolved), then Opportunities with Record Type and Sales Process assigned, then Cases, then Campaigns and CampaignMembers, then Activities (Tasks, Events, EmailMessages via Bulk API 2.0 with chunking), then Custom Entities in topological order, then Notes and Attachments.

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins. EspoCRM's 200-record API ceiling is handled through paginated extraction loops with configurable maxSize.

  6. Cutover, validation, and automation rebuild handoff

    We freeze EspoCRM writes 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 and BPM inventory document to the customer's admin team. We support a one-week hypercare window where we resolve reconciliation issues raised by the customer's team. We do not rebuild EspoCRM Workflows or Advanced Pack BPM processes as Salesforce Flow inside the migration scope; that is a separate engagement or an internal admin task.

EspoCRM Salesforce
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · SalesforceRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

4-6 weeksTypical, smaller accounts
10-14 weeksLarge or heavily customised accounts

A quote scales with record volume, custom entity count and dependency complexity, and whether the EspoCRM instance is self-hosted (requiring filesystem file transfer) or cloud-hosted. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for EspoCRM to Salesforce →

Why teams move from EspoCRM to Salesforce

  • EspoCRM's integration ecosystem is narrow compared to Salesforce's AppExchange. Official integrations are limited to Google Workspace, Outlook, Zoom, VoIP, and Stripe, while Salesforce AppExchange lists over 9,000 certified applications including native ERP connectors, CPQ, contract lifecycle management, and revenue intelligence tools. Teams that need deep integrations with NetSuite, SAP, Oracle, DocuSign CLM, or Apttus move to Salesforce because the connections are first-party or AppExchange-certified rather than custom-coded alternatives.
  • EspoCRM requires increasing technical knowledge for complex customizations. G2 and Capterra reviewers report that complex entity relationships and custom PHP/Before-Save scripts become difficult to maintain across upgrades. Salesforce's AppExchange partner ecosystem and the Trailblazer community provide documented patterns for complex requirements without requiring custom PHP code or server-side scripting.
  • EspoCRM performance degrades on large datasets without server-side tuning. Teams with hundreds of thousands of records report slow list views and degraded search performance, particularly on self-hosted instances without dedicated server resources. Salesforce's multi-tenant infrastructure handles large record volumes without requiring customers to manage server performance tuning, which shifts infrastructure responsibility to Salesforce rather than an internal IT team.
  • EspoCRM's email and SMS functionality requires third-party integrations and does not work natively out of the box. Teams expecting a complete CRM experience are frustrated by the need to configure Google Workspace, Outlook, or third-party VoIP integrations for basic sales communication features. Salesforce Sales Cloud includes native email-to-lead, email logging, and activity tracking without additional integrations for most use cases.
  • EspoCRM carries 0.01% market share compared to Salesforce's 25.29% in the CRM Platforms category. Enterprise procurement, IT governance, and security review teams often mandate Salesforce as the approved CRM vendor due to its SOC 2 compliance, GDPR data processing agreements, and enterprise SLA coverage. Teams moving through procurement or security review processes migrate to Salesforce to satisfy internal compliance requirements that EspoCRM's smaller footprint does not address.

Questions, answered

EspoCRM to Salesforce migration questions

How long does an EspoCRM to Salesforce migration take?

Most migrations land between four and six weeks for accounts under 15,000 Contacts and 3,000 Opportunities with no custom entities or minimal attachment volumes. Migrations with multiple custom entity types that reference each other, large attachment volumes (thousands of files on self-hosted instances), or engagement histories over 200,000 activity records move to ten to fourteen weeks because of dependency graph analysis, filesystem extraction, Bulk API chunking, and Validation Rule coordination.

Do EspoCRM Workflows, BPM processes, and custom scripts migrate to Salesforce Flow?

No. EspoCRM's Advanced Pack BPM and Workflow automation features are structurally different from Salesforce Flow. Workflow rules, BPM processes, and custom PHP/Before-Save scripts do not migrate as code. We deliver a written inventory of every active EspoCRM Workflow and BPM process with its trigger, conditions, actions, and a recommended Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds them post-migration. Custom PHP scripts are outside the scope of any automated migration tool.

Can we migrate files stored on EspoCRM's filesystem?

Yes, but it requires a separate extraction step. On self-hosted EspoCRM instances, uploaded files are stored on the server filesystem under the data/files/ directory rather than in the database. We identify all Attachment records during discovery, extract the referenced files from the filesystem archive, and upload them to Salesforce as ContentVersion records linked to the corresponding Contact, Account, Opportunity, Case, or custom object. Cloud-hosted EspoCRM instances store files in the database and migrate with the standard database export without a separate filesystem step.

Do we lose historical activity data (calls, emails, meetings, tasks)?

No. We migrate the full activity history. Calls land as Task records with TaskSubtype=Call; meetings land as Event records with attendees as EventRelation records; emails land as EmailMessage records linked to Tasks; tasks land as Task records. Activity timeline ordering is preserved by setting ActivityDate to the original EspoCRM timestamp. Notes migrate as Salesforce Note records. The EspoCRM 200-record API ceiling is handled through paginated extraction loops to ensure all records are captured regardless of volume.

How do we handle EspoCRM custom entities created with Entity Manager?

EspoCRM custom entity types created via Entity Manager migrate to Salesforce Custom Objects with a __c suffix. We export the entityDefs metadata (field names, types, relationships) from EspoCRM first, pre-create the destination Salesforce schema, then migrate records in dependency order. If custom entities reference each other, we build a dependency graph and import in topological order so that parent records exist before child records are inserted. Junction entities (many-to-many join tables) map to Salesforce junction objects with two Lookup fields.

What happens if Salesforce Validation Rules block the import?

We coordinate with the destination Salesforce admin before migration to identify active Validation Rules that could block inserts. We either temporarily disable the rules during the migration window (and re-enable them post-migration) or extend them with a migration-context bypass condition. Without this coordination, Validation Rules commonly reject 5-30 percent of records on first import attempt, requiring iterative correction passes that extend timeline and cost.

Can FlitStack AI migrate EspoCRM data to a specific Salesforce org (not a new tenant)?

Yes. We migrate to the customer's existing Salesforce org rather than provisioning a new tenant. We work with the destination org's current schema, Validation Rules, field-level security profiles, and Record Types. If the destination org has an existing data model (Accounts, Contacts, Opportunities already present), we perform a dedupe analysis to determine whether EspoCRM records should merge with existing records by matching on email, company name, or another customer-specified key, or whether they should import as new records alongside the existing data.

Get a quote

Moving from EspoCRM 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