Civicrm to Salesforce migration
We migrate Contacts, Activities, Contributions, Memberships, and Cases from CiviCRM into Salesforce with the Activity-to-pipeline translation resolved up front, multi-record custom fields mapped to custom objects with schema-aware field names, and every CiviCase status enumerated and individually mapped to the destination case status set before cutover.
FlitStack AI migrates contact and accounts, contact relationships, task and events, opportunity or custom objects and npe5__membership__c or custom objects from Civicrm 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: 3-5 weeks.

What moves from Civicrm to Salesforce?
Moving from CiviCRM to Salesforce is a schema translation and object remapping project, not a record copy.
Read the full summary
CiviCRM uses a nonprofit-native data model with Contributions, Memberships, Events, and Cases as first-class entities, while Salesforce is a general CRM where those objects require either the Nonprofit Success Pack (NPSP) extension or a custom object configuration to replicate. We handle both paths: NPSP-aware migrations map Contributions to Opportunities and Memberships to Recurring Donations and Membership records, while non-NPSP destinations map to custom objects with equivalent fields. CiviCRM has no native pipeline or deal object; Activity-based fundraising workflows translate into Salesforce Opportunities using the activity timeline as the source of truth for pipeline stages and amounts. Multi-record custom fields land as separate custom objects prefixed with Custom_, and ECK (Entity Construction Kit) entities are flagged as extension-scoped schemas requiring manual destination schema design. CiviMail mailing records and CiviRules automated processes do not migrate; we deliver a written inventory of each for the customer's admin to rebuild.
Contact (Individual, Household, Organization) → Contact and Account
CiviCRM Contact subtypes (Individual, Household, Organization) map to Salesforce Contact with subtype preserved in a custom field civicrm_contact_type__c.
How it maps
Household contacts generate Salesforce Household Accounts via the NPSP Household model if installed, or standard Account records if not. Organization contacts map to Salesforce Account directly. We preserve all standard address blocks (street, city, state, postal code, country), email, phone, and relationship links. The CiviCRM display_name becomes Contact Name, and the CiviCRM sort_name becomes a custom field for alphabetical ordering.
Relationship → Contact Relationship
CiviCRM Relationships (household member, employee-employer, spousal, and custom relationship types) map to Salesforce Contact Relationship records.
How it maps
We preserve the relationship type label, both contact references (contact_id_a and contact_id_b), and the is_active flag. Bidirectional relationship types generate two Contact Relationship records in Salesforce. The relationship start and end dates migrate as custom fields on Contact Relationship if the destination org uses the NPSP relationship model.
Activity → Task and Event
CiviCRM Activities (the catch-all engagement record for calls, emails, meetings, tasks, and custom activity types) map to Salesforce Task and Event objects.
How it maps
Activity type determines the destination object: email maps to Task with Subject and Description; call maps to Task with TaskSubtype=Call; meeting maps to Event with StartDateTime and EndDateTime. Custom activity types from CiviCRM become custom Task or Event record types. We set ActivityDate on Task and StartDateTime on Event to the original CiviCRM activity_date_time for timeline ordering. The activity's assignees ( civicrm_activity_contact with record_type = 3 ) resolve to Salesforce OwnerId via email match.
Contribution → Opportunity (NPSP) or Custom Object
CiviCRM Contributions include financial_type, total_amount, currency, receive_date, and payment_instrument.
How it maps
If the destination Salesforce org uses NPSP, Contributions map to Opportunity with NPSP-specific fields (npe01__Amount__c, npe01__Payment_Method__c, npe01__Check_Number__c). If NPSP is not installed, we map Contributions to a custom object with equivalent fields and a lookup to the Contact. Price sets introduce variable line-item complexity that must be flattened: each price field value becomes a separate Opportunity Product line or a custom Contribution_Line_Item__c record. We resolve the financial_type to a Campaign or custom field for segregation.
Membership → npe5__Membership__c (NPSP) or Custom Object
CiviCRM Membership records include type, status, start_date, end_date, and source.
How it maps
With NPSP, these map to the standard Membership object (npe5__Membership__c) with a lookup to the Contact and a separate Membership Type record. Membership Price Sets allow complex tier structures that must be mapped to the destination membership tier configuration. Without NPSP, Memberships migrate as a custom object with equivalent fields and the membership status mapped to a custom picklist. The membership_id is preserved as a custom field for reconciliation.
Group and GroupContact → Campaign and CampaignMember (or Custom Object)
CiviCRM Groups and their membership lists (GroupContact) are migrated as static segments.
How it maps
Each CiviCRM Group becomes a Salesforce Campaign with Campaign Member status values representing the original group membership records. We preserve the group hierarchy where it exists using Campaign parent-child relationships. Dynamic (smart) groups that are rebuilt on query conditions cannot be fully reproduced without re-running the query logic in Salesforce; we document each dynamic group definition and recommend Salesforce Reports or Campaign membership filters as the equivalent.
- ContactContact and Accountsplit
- RelationshipContact Relationship1:1
- ActivityTask and Event1:1
- ContributionOpportunity or Custom Objecttransformed
- Membershipnpe5__Membership__c or Custom Object1:1
- Group and GroupContactCampaign and CampaignMember1:1
+ 9 more in the mapping below
How Civicrm and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Civicrm | Salesforce |
|---|---|---|
| CRM architecture | Open-source nonprofit CRM with no per-seat or per-contact license cost; requires PHP/MySQL hosting | Per-user SaaS CRM with tiered licensing; Salesforce.org offers 10 free licenses for nonprofits with paid plans at $36/user/mo Essentials upward |
| Nonprofit-native objects | Contributions, Memberships, Grants, Events, and Cases as built-in first-class entities | Salesforce core has no native donation or membership object; NPSP extension adds these or they must be custom-built |
| Pipeline and deals | No native pipeline or deal object; organizations use Activity-based workflows to track fundraising | Opportunity object with Stage, Amount, CloseDate, and multiple sales processes from the core platform |
| Custom data model | Custom fields, multi-record sets, and ECK entities for arbitrary organizational schemas | Custom objects and fields with __c suffix; unlimited from Professional tier ($80/user/mo) upward |
| CMS integration | Native integration with Drupal, WordPress, Joomla, and Backdrop CMS platforms | No native CMS integration; requires third-party connectors or Experience Cloud for portal-style access |
| Export tooling | No native bulk export; API or direct MySQL access required for data portability | Data Export Wizard, Data Loader, and Bulk API 2.0 for structured data extraction and import |
| Pricing predictability | Free open-source; hosting costs only; no per-seat or per-contact billing | Per-user model with increasing feature tiers; 10 free nonprofit licenses offset but grow unpredictably at scale |
What to watch for in a Civicrm to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
CiviCase statuses are type-scoped, not global
CiviCase defines statuses within each case_type definition via XML or PHP entityType.
How we handle it
When migrating Cases, we must enumerate every active case_type, extract its status option values, and map them individually to the destination case status set. Status IDs are not global integers in CiviCRM; they are type-scoped. Mixing status values across case types during import produces silent mis-assignments where a case shows the wrong status without throwing an error. We handle this by building a per-case-type status map during scoping and enforcing type-scoping in the migration transform. Without this, a Case for a Grant Application case_type might receive a status value intended for an Intake case_type.
Multi-record custom groups can exceed MySQL join limits in APIv4
CiviCRM APIv4's custom.* wildcard selector adds one join per custom group.
How we handle it
Sites with more than approximately 20 custom groups exceed MySQL's maximum join count, causing a fatal error during export. We query the custom group count during scoping and fall back to individual entity-by-entity exports for sites at risk. This increases migration time for large custom-field-heavy instances and requires read-only database credentials scoped to the CiviCRM database in addition to API access.
CiviMail and automated processes do not migrate
CiviMail mailing records are tightly coupled to the SMTP configuration, SPF/DKIM domain authentication, and the CMS integration of the source CiviCRM instance.
How we handle it
Extracting mailing records and delivery statistics does not reproduce the mailing infrastructure in Salesforce, which has its own email deliverability configuration. We do not migrate CiviMail records. We deliver a written inventory of mailing subjects, audience sizes, and send dates for reference. Similarly, CiviRules automated processes (CiviCRM's workflow automation extension) do not migrate to Salesforce Flow; we deliver a written map of every CiviRules rule with its trigger, conditions, and actions for the customer's admin to rebuild in Salesforce Flow.
ECK entities require manual destination schema design
ECK (Entity Construction Kit) entities are arbitrary custom schemas built by the CiviCRM administrator to model organizational workflows that have no standard CiviCRM equivalent.
How we handle it
Because these schemas are extension-scoped and user-defined, there is no automatic mapping to Salesforce objects. We enumerate every active ECK entity type, its properties, and its contact reference fields during scoping and present them as a schema design exercise for the customer. Each ECK entity becomes a Salesforce custom object, but the customer must approve the field types, picklist values, and lookup relationships before we build the destination schema. This adds a design gate to the migration timeline that standard object migrations do not have.
No native bulk export requires hybrid extraction strategy
CiviCRM has no one-click comprehensive export.
How we handle it
Data portability depends on the REST API (paginated, session-key or API-key authenticated) or direct MySQL access. We use a hybrid approach: API-first for Contacts and Activities, with direct database reads for large-volume custom tables where API pagination would be prohibitively slow. This requires read-only database credentials scoped to the CiviCRM database. For self-hosted CiviCRM instances with no accessible database (managed hosting with restricted MySQL access), we are limited to API extraction, which increases migration time for large record volumes. We flag this constraint during scoping so the customer can provision database access or accept the API-only extraction timeline.
How the migration runs
Discovery and data audit
We audit the source CiviCRM instance across version, CMS integration (Drupal, WordPress, Joomla, Backdrop), installed extensions (CiviCase, CiviGrant, CiviMail, CiviRules, ECK), and data volume for each entity type.
What this step covers
We identify the contact subtype distribution (Individual, Household, Organization), count active custom groups and ECK entity types, enumerate every CiviCase case_type and its status options, and assess the contribution price set complexity. We also identify whether the destination Salesforce org has NPSP installed or requires custom object configuration for nonprofit entities. The discovery output is a written migration scope with entity counts, custom field inventory, and a recommendation on NPSP vs. custom object strategy.
Database and API access provisioning
We establish read access to the CiviCRM data.
What this step covers
For self-hosted instances, this includes read-only database credentials scoped to the CiviCRM database for bulk custom table extraction and API key or session-key credentials for paginated API access. For CiviSpark managed hosting, we use the documented REST API only (no direct database access). We run a burst test of 500 API requests to measure the effective throttle ceiling and calibrate our worker throttling accordingly. If MySQL join limits are detected during custom field enumeration (more than 20 custom groups), we document the fallback to entity-by-entity exports.
Schema design and case status enumeration
We design the destination Salesforce schema.
What this step covers
For NPSP destinations, we configure NPSP Data Import field mappings for Contacts, Contributions, Memberships, and Households. For non-NPSP destinations, we create custom objects with equivalent fields for Contributions, Memberships, and Grants. We enumerate every CiviCase case_type and its status options and map them to Salesforce Case Status values or custom status sets. For ECK entities, we present a schema design document to the customer for approval before creating the custom objects. We create the Salesforce schema in a Sandbox org first for validation.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox using production-like data volume.
What this step covers
The customer's nonprofit operations lead reconciles record counts (Contacts in vs. Leads/Contacts out, Contributions in vs. Opportunities out, Activities in vs. Tasks/Events out), spot-checks 25-50 random records against the CiviCRM source, and validates that CiviCase statuses are correctly assigned per case_type. Any mapping corrections, particularly for ECK entities and custom price set structures, happen here. The customer signs off on the Sandbox migration before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Custom Objects schema first (for ECK entities and custom nonprofit objects), then Contacts (with subtype split and relationship resolution), then Accounts (for Organization contacts), then Groups to Campaigns, then Activities to Tasks and Events, then Contributions to Opportunities, then Memberships, then Cases (with per-type status resolution), then Attachments to ContentDocument, then Tags to Topics.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. Large engagement histories use Salesforce Bulk API 2.0 with batch chunking and exponential backoff on API limit responses.
Cutover, validation, and automation handoff
We freeze CiviCRM 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 CiviMail inventory document (mailing subjects, audience sizes, send dates) and the CiviRules automation map (rules, triggers, conditions, actions with Salesforce Flow equivalents) to the customer's admin team. We support a one-week hypercare window where we resolve reconciliation issues. We do not rebuild CiviMail infrastructure or CiviRules automations as Salesforce Flow inside the migration scope; that is a separate engagement or an internal admin task.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom object count, and whether the destination Salesforce org uses the Nonprofit Success Pack (NPSP) or requires custom object configuration for Contributions and Memberships. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Civicrm to Salesforce →Why teams move from Civicrm to Salesforce
- Salesforce is the industry-standard CRM with the broadest integration ecosystem and the largest pool of certified implementers for nonprofits. Salesforce.org's Nonprofit Cloud extends the core platform with donor management, volunteer tracking, and program outcomes tools purpose-built for mission-driven organizations. Reviewers on G2 and Capterra cite the depth of the Salesforce partner ecosystem as a reason to move away from CiviCRM, particularly when organizations outgrow their internal technical capacity and need a certified partner rather than a community consultant.
- CiviCRM's technical overhead becomes prohibitive for organizations without a dedicated PHP developer or consultant. Multiple G2 and Capterra reviews note that configuring CiviCRM well requires developer resources that small and mid-sized nonprofits cannot sustain. Salesforce's point-and-click admin tools, Salesforce Setup menu, and declarative automation (Flow, Process Builder) reduce the developer dependency that drives CiviCRM maintenance costs beyond the initial implementation.
- CiviCRM's free open-source model has hidden infrastructure and maintenance costs that become visible at scale. Server costs, PHP/MySQL maintenance, security patching, API rate limit tuning, and CiviCRM upgrade script execution fall on the organization's technical team. Salesforce is a managed SaaS platform where infrastructure, performance tuning, and platform upgrades are handled by Salesforce. For organizations comparing total cost of ownership rather than license cost alone, Salesforce's per-user pricing often undercuts the fully-loaded cost of a well-configured CiviCRM deployment.
- Salesforce's reporting engine is purpose-built for multi-dimensional pipeline analysis across territories, product lines, and fiscal periods. CiviCRM's reporting capabilities suit basic nonprofit use cases but reviewers on G2 and Capterra describe advanced segmentation, custom report types, and cross-object analytics as requiring SearchKit knowledge or developer assistance that most nonprofit staff teams do not have in-house. Organizations with complex grant reporting requirements, multi-program attribution, or donor cohort analysis move to Salesforce for reporting flexibility without custom development.
- Salesforce AppExchange offers over 9,000 apps including purpose-built nonprofit fundraising, grant management, and volunteer coordination tools. CiviCRM's extension ecosystem is smaller and community-maintained, meaning some integrations require custom development that would be available as packaged AppExchange products in Salesforce. Organizations that need integrated email marketing, peer-to-peer fundraising, or event ticketing tools that integrate with their CRM move to Salesforce to access the AppExchange catalog without building custom integrations from scratch.
Questions, answered
Civicrm to Salesforce migration questions
How long does a CiviCRM to Salesforce migration take?
Most CiviCRM migrations land between three and five weeks for instances under 10,000 Contacts with no ECK entities, fewer than 20 custom groups, and straightforward case type configurations. Migrations with large activity histories (over 200,000 records), complex multi-record custom groups requiring entity-by-entity exports, ECK entities with cross-contact lookups, or multiple CiviCase case_types with distinct status sets move to eight to fourteen weeks because of the additional scoping, per-case-type status enumeration, and ECK schema design work required before migration runs.
Do CiviMail mailing records and CiviRules automations migrate to Salesforce?
No. CiviMail mailing records are tightly coupled to the source CiviCRM's SMTP configuration, SPF/DKIM domain settings, and CMS integration, and cannot be extracted and reproduced independently in Salesforce's email deliverability environment. We do not migrate them. We deliver a written inventory of every CiviMail mailing with its subject, recipient group count, send date, and open rate for the customer's admin to use when rebuilding email templates and audience segments in Salesforce Marketing Cloud or their chosen marketing platform. CiviRules automated processes (CiviCRM's workflow automation extension) similarly do not migrate; we deliver a written map of every CiviRules rule with its trigger, conditions, and actions and a recommended Salesforce Flow equivalent.
Can we migrate CiviCRM Contributions and Memberships without NPSP?
Yes. We map Contributions to a custom Opportunity object with fields for amount, currency, payment method, financial type, and receive date. Memberships map to a custom Membership__c object with fields for type, status, start date, end date, and source. The advantage of NPSP is that these objects are pre-built and validated for Salesforce reporting and Household modeling, but they are not required for a successful migration. We discuss NPSP vs. custom object strategy during scoping and make a recommendation based on the destination org's existing configuration and the customer's reporting requirements.
How do you handle CiviCRM's lack of native bulk export?
CiviCRM has no one-click comprehensive export. We use a hybrid extraction strategy: API-first for Contacts, Activities, and standard entities via the CiviCRM REST API (paginated with API-key or session-key authentication), with direct database reads for large-volume custom tables where API pagination would be prohibitively slow. This requires read-only database credentials scoped to the CiviCRM database. For managed CiviSpark hosting with no database access, we are limited to API extraction, which increases migration time for large instances. We flag this constraint during scoping so the customer can provision database access if needed.
Do we keep CiviCRM for email and move only the CRM data to Salesforce?
Yes. A common migration pattern is to move the CRM data (Contacts, Contributions, Memberships, Cases) to Salesforce while keeping CiviCRM running specifically for CiviMail email campaigns (because CiviCRM's native CMS integration makes email-from-the-database more accessible than Salesforce's marketing tools without Marketing Cloud). We migrate the CRM objects to Salesforce and document the CiviMail mailing history separately. The customer continues sending email from CiviCRM while using Salesforce for donor management, reporting, and program tracking. Over time, most organizations migrate email to Salesforce Marketing Cloud or another dedicated marketing platform.
What happens to our ECK entities during migration?
ECK (Entity Construction Kit) entities are arbitrary custom schemas that CiviCRM administrators build to model organizational workflows beyond what standard CiviCRM entities cover. They have no automatic mapping to Salesforce because they are extension-scoped and user-defined. During scoping, we enumerate every active ECK entity type, its properties, and its contact reference fields. We present each ECK entity as a custom object design exercise: the customer reviews the CiviCRM schema and approves the Salesforce custom object fields, field types, and lookups before we build the destination schema. This adds a design gate to the timeline that standard entity migrations do not have, but it ensures that ECK data is not lost or mis-modeled during migration.
How do you preserve CiviCase history and timeline during migration?
CiviCase records include the case itself (case_id, case_type, status, start_date) and a chain of related activities (the case timeline). We migrate both: the Case record maps to Salesforce Case or a custom object, and every related Activity maps to a Salesforce Task or Event linked to the Case via WhatId. Activity timeline ordering is preserved by setting ActivityDate to the original CiviCRM activity_date_time. Case status assignment requires the per-case-type status enumeration work during scoping: we extract the status values from each active case_type definition and map them individually to the destination status set before any case data loads. This prevents silent mis-assignment of case statuses across different case types.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Sentia to SalesforceMapping · history · rollbackWise Agent to SalesforceMapping · history · rollbackKeap to SalesforceMapping · history · rollbackKartra to SalesforceMapping · history · rollbackMarketing Star to SalesforceMapping · history · rollbackYardi to SalesforceMapping · history · rollback Civicrm to Dynamics 365Mapping · history · rollbackCivicrm to HubSpotMapping · history · rollbackCivicrm to PipedriveMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from Civicrm 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