Skip to content
Get a quote

SuiteCRM to Salesforce migration

We migrate Accounts, Contacts, Leads, Opportunities, and custom modules from SuiteCRM into Salesforce Sales Cloud with the v4.1 REST or v8 API extraction strategy chosen at discovery, relationship chains resolved before import, and every Studio-defined custom field mapped to a typed Salesforce field before cutover.

Short answer

FlitStack AI migrates accounts, contacts, leads, opportunities and product2s from SuiteCRM 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.

By

Source SuiteCRM
DestinationSalesforce
AccountContactLeadOpportunityProduct2
Mapped field by field · sample run · one-click rollback

What moves from SuiteCRM to Salesforce?

Moving from SuiteCRM to Salesforce Sales Cloud is a cross-platform migration that requires navigating SuiteCRM's PHP-based schema, filesystem-attached Documents, custom workflow definitions stored as serialized PHP, and an API extraction path that differs between 7.x and 8.x instances.

Read the full summary

We identify the SuiteCRM version at discovery and apply the appropriate export method — v4.1 SOAP for legacy 7.x instances and v8 REST for 8.x — before any data is extracted. Custom fields added via Studio are stored in extended database tables and must be enumerated separately from the standard schema. Documents live on the server filesystem, not the database, so filesystem integrity is validated alongside the record export. We do not migrate AOW Workflows as code; we deliver a JSON inventory of every rule for manual rebuild in Salesforce Flow. SuiteCRM Users map to Salesforce Users by email lookup, and owner resolution must complete before any record import begins.

1:1

Accounts → Account

SuiteCRM Accounts map directly to Salesforce Account.

How it maps

Name, industry, website, billing address, and phone migrate as standard fields. We use Account Name as the dedupe key during import. Account is created before any Contact import so that the AccountId Lookup is satisfied at the moment of Contact insert. If SuiteCRM uses a custom Account naming convention, we flag it during scoping for the customer's admin to review.

1:1

Contacts → Contact

SuiteCRM Contacts map to Salesforce Contact.

How it maps

Standard name, email, phone, title, and the primary Account link migrate directly. We resolve AccountId by matching the SuiteCRM account_name relationship to the Salesforce Account record created in the prior phase. Custom fields added via Studio are enumerated from the SuiteCRM database vardefs and mapped to Salesforce custom fields of equivalent type.

1:1

Leads → Lead

SuiteCRM Leads map to Salesforce Lead.

How it maps

Lead status, lead source, and assignment fields migrate as standard fields. Any converted leads in SuiteCRM (where status = 'Converted') require a decision at scoping — the original Lead record in SuiteCRM has no direct Salesforce equivalent for conversion history, so we migrate the pre-conversion Lead record and flag that the conversion metadata is a manual review item post-migration.

1:1

Opportunities → Opportunity

SuiteCRM Opportunities map to Salesforce Opportunity.

How it maps

Revenue amount, sales stage, close date, and parent Account link migrate directly. Stage probability percentages are mapped to Salesforce StageProbability values. We configure Salesforce Record Types and Sales Processes before migration so that the correct stage values are whitelisted per record type.

1:1

Products → Product2

SuiteCRM Products catalogue maps to Salesforce Product2 records with Standard Price Book entries created during import.

How it maps

ProductCode, description, and pricing migrate. Products must be imported before Quotes and Line Items to satisfy the Pricebook2 reference on child records.

1:1

Quotes → Quote

SuiteCRM Quotes map to Salesforce Quote, which is available from the Professional tier.

How it maps

Quote body, line items, and Opportunity linkage migrate. PDF exports are extracted as ContentDocument records and attached to the Quote in Salesforce. We flag Quote Record Type configuration if the customer uses multiple quote templates per pipeline.

What moves15 objects
SuiteCRMSalesforce
  • AccountsAccount1:1
  • ContactsContact1:1
  • LeadsLead1:1
  • OpportunitiesOpportunity1:1
  • ProductsProduct21:1
  • QuotesQuote1:1

+ 9 more in the mapping below

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

DimensionSuiteCRMSalesforce
ArchitectureSelf-hosted PHP application with database on customer serverSaaS multitenant cloud platform with metadata-driven schema
Lead modelSeparate Leads module from Contacts; no Lead Convert flowSeparate Lead and Contact with explicit Convert action to Account and Contact
Custom field storageExtended database tables with Studio-appended naming conventionCustom fields with __c suffix in the same object table via metadata API
Document storageFiles on server filesystem (/upload/) with DB metadata referenceContentDocument and ContentVersion in Salesforce Files with library management
Pricing modelFlat-rate Community Edition (free) or hosted tiers; unlimited usersPer-user Enterprise Agreement tiers from $80/user/month at Professional
Workflow automationAOW module with PHP-serialized rule definitions not accessible via APISalesforce Flow with record-triggered, scheduled, and screen variants from Professional
Version upgrade risk7.x to 8.x migration silently breaks web UI (documented community failures)Three release updates per year with sandbox validation before each

What to watch for in a SuiteCRM 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

7.x instances require v4.1 SOAP or database export, not v8 REST

SuiteCRM 8 introduced the v8 REST API, but 7.x instances do not expose it.

How we handle it

We identify the current SuiteCRM version during discovery. For 7.x instances, we extract via the v4.1 SOAP API or direct MySQL database export if the SOAP endpoint is unavailable or throttled. For 8.x instances, we use the v8 REST API. Skipping this version check means using the wrong extraction method, which either returns empty record sets or times out mid-export. If a customer plans to upgrade from 7.x to 8.x before migrating, we recommend completing the data migration first to avoid compounding upgrade risk with migration risk simultaneously.

high

Document files live on the filesystem, not the database

SuiteCRM's Documents module saves files to the server upload directory, not as database blobs.

How we handle it

A pure API or database-record export misses the files entirely. We include a filesystem copy step that extracts all files from the upload directory, validates file integrity checksums, preserves directory structure, and restores them as Salesforce ContentVersion records. File permissions (owner, group, read/write bits) must be preserved during extraction or files become inaccessible after the move. We flag this as a mandatory step in every SuiteCRM export plan.

medium

AOW Workflow definitions cannot be programmatically exported

SuiteCRM's Advanced Open Workflow module stores automation rules as PHP-serialized objects in the database.

How we handle it

These definitions are not accessible via the REST or SOAP API in a reusable format, and the serialized format is not portable to Salesforce Flow. We export a human-readable JSON summary of each AOW rule — module, trigger conditions, actions, and execution order — as a reference document for the customer's admin to rebuild in Salesforce Flow post-migration. The rules themselves must be rebuilt from scratch; we do not treat them as transferable automation logic.

medium

Picklist values must match exactly between SuiteCRM and Salesforce

SuiteCRM picklist values are stored as database-level strings with no enforced relationship to a separate picklist metadata table in many 7.x deployments.

How we handle it

When migrating to Salesforce, every picklist value in SuiteCRM must exist in the Salesforce picklist definition before records import or those records will be rejected with a validation error. We enumerate all picklist values during discovery, pre-create the Salesforce picklist values in the destination org (or flag mismatches for manual resolution), and run a pre-flight validation pass before record import begins.

low

Version 7.x extended support ends mid-2027 on ESR branch

SuiteCRM 7.15 ESR extends 7.x support into 2027, but standard 7.x releases have already lost community support coverage.

How we handle it

Customers running older 7.x branches face security vulnerabilities with no patches available. We flag the version at scoping — customers on pre-ESR 7.x branches should either upgrade to 7.15 ESR before migration begins or plan a cutover before the ESR branch support window closes. This also affects which extraction method we use, as noted in gotcha one.

How the migration runs

  1. Discovery and version identification

    We audit the source SuiteCRM instance: version (7.x or 8.x, and specific sub-release), hosting model (self-hosted or SuiteCRM-hosted), custom modules and Studio-defined fields, active AOW workflow count and complexity, document file volume and directory structure, and record counts across all modules.

    What this step covers

    We identify the correct extraction path — v4.1 SOAP for 7.x, v8 REST for 8.x, or direct MySQL export for edge cases where the API is unavailable. The discovery output is a written migration scope document with a record-count table, extraction method recommendation, and Salesforce edition guidance.

  2. Salesforce destination schema design

    We design the Salesforce destination schema in a Sandbox org.

    What this step covers

    This includes provisioning custom objects (with __c API names matched to SuiteCRM custom module names), custom fields for all Studio-defined extensions, Record Types and Sales Processes per pipeline, Page Layouts per Record Type, and picklist value definitions matched exactly to the source SuiteCRM picklists. Schema is deployed via metadata API into Sandbox for validation before any records are loaded.

  3. Filesystem and API extraction

    We extract SuiteCRM data in parallel tracks: the REST or SOAP API for record data (Accounts, Contacts, Leads, Opportunities, custom modules), and the server filesystem for Document files in the upload directory.

    What this step covers

    File checksums are validated after extraction. For 7.x instances, we also enumerate custom field definitions from the database vardefs directly if the API does not expose them. This extraction phase produces a structured export package with a manifest file per object.

  4. Sandbox migration and reconciliation

    We run a full migration into a Salesforce Sandbox using production-equivalent data volume.

    What this step covers

    The customer's admin reviews record counts, spot-checks 25-50 records per module against the SuiteCRM source, and validates picklist rendering, custom field values, and relationship links. Any mapping corrections — picklist value mismatches, missing custom fields, relationship resolution failures — are corrected before the Sandbox sign-off and before production migration begins.

  5. Owner reconciliation and User provisioning

    We extract every distinct SuiteCRM User referenced on records and match by email against the Salesforce destination org's User table.

    What this step covers

    Unmatched users go to a reconciliation queue. The customer's Salesforce admin provisions any missing Users. This step is mandatory before record import because OwnerId references are required on most standard objects. We do not migrate SuiteCRM user permissions, role hierarchies, or team assignments — these are rebuilt in Salesforce Profiles and Permission Sets post-migration.

  6. Production migration in dependency order

    We run production migration in record-dependency order: Files (ContentVersion via Bulk API), Accounts (from SuiteCRM Accounts), Contacts (with AccountId resolved), Leads, Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Products and Pricebook entries, Quotes, Contracts, Cases, Campaigns (with CampaignMember import), Activity history (Tasks, Events, Notes via Bulk API 2.0), Custom Objects (last, after all lookup targets are present).

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins. We freeze SuiteCRM writes during the cutover window and run a final delta migration of any records modified during the migration period.

  7. Cutover, validation, and automation rebuild handoff

    We validate the production Salesforce org against the reconciliation baseline: record counts per object, spot-check sampling, relationship integrity (AccountId on Contact, WhatId on Task), and ContentDocument linkage for migrated files.

    What this step covers

    We deliver the AOW Workflow inventory JSON document to the customer's admin team with a recommended Salesforce Flow equivalent for each rule. We support a one-week hypercare window for reconciliation issues. We do not rebuild AOW workflows as Salesforce Flow inside the migration scope; that is a separate engagement or an internal admin task. Salesforce Profiles, Permission Sets, and role hierarchy are similarly out of scope and require the customer's admin to configure from the SuiteCRM roles and teams reference.

SuiteCRM 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

3-5 weeksTypical, smaller accounts
8-14 weeksLarge or heavily customised accounts

A quote scales with record volume, custom module count, and whether the SuiteCRM instance is 7.x (requiring v4.1 SOAP API extraction) or 8.x (v8 REST). Every quote is scoped with you; there is no self-serve pricing.

Get a quote for SuiteCRM to Salesforce →

Why teams move from SuiteCRM to Salesforce

  • SuiteCRM requires a technical resource to maintain, and that DevOps overhead grows with scale. Reviewers on Reddit and G2 consistently cite the cost of self-hosting — server provisioning, security patching, PHP upgrades, failed version upgrades — as a hidden cost that erases the licensing savings over a three-year horizon. Salesforce Sales Cloud removes the infrastructure burden entirely, replacing server costs with per-user subscription pricing that includes SLA-backed uptime and a managed release cadence.
  • The SuiteCRM 7.x to 8.x architectural upgrade has caused widespread web UI failures in the community — missing CSS, broken JS, and permissions resets — even when the terminal reports a successful upgrade. Teams that deferred migration now face an unsupported 7.x branch with community-only patches. Salesforce's three annual releases include sandbox validation, automated testing tools, and rollback capability, removing the version-upgrade risk that makes SuiteCRM upgrades a maintenance liability rather than a routine upgrade.
  • SuiteCRM's UI is widely described as outdated, slow, and clunky compared to modern SaaS CRMs. The mobile app is a web wrapper with poor offline performance. Salesforce's Lightning Experience delivers a responsive, mobile-native interface, and its AppExchange ecosystem (over 9,000 listings) provides integrations that are first-party or certified rather than community-maintained add-ons with unreliable sync behaviour. Sales teams using SuiteCRM cite the UI as a daily friction point that Salesforce resolves out of the box.
  • Google Calendar integration and other third-party connectors are unreliable in SuiteCRM in day-to-day use, causing sync failures that frustrate field sales teams. Salesforce offers native integrations with Google Workspace and Microsoft 365 at the platform level, plus a certified AppExchange integration catalog that reduces integration maintenance to a managed app install rather than a PHP configuration task.
  • Salesforce's reporting engine supports multi-dimensional pipeline analysis across territories, product lines, custom fiscal periods, and non-standard attribution models. SuiteCRM's reporting module is functional for basic roll-ups but constrains complex sales analysis, requiring teams to export to spreadsheets for territory reporting and board-level dashboards. Enterprise revenue operations teams cite Salesforce's reporting depth as a primary driver for switching from SuiteCRM.

Questions, answered

SuiteCRM to Salesforce migration questions

How long does a SuiteCRM to Salesforce migration take?

Most migrations land between three and five weeks for accounts with under 20,000 Accounts, 40,000 Contacts, and no more than two or three custom modules. Migrations with multiple custom modules, large document collections, or 7.x instances requiring v4.1 SOAP extraction move to eight to fourteen weeks because of filesystem extraction steps, custom schema enumeration, and relationship resolution across custom join tables.

Do SuiteCRM AOW Workflows and Studio automation rules migrate to Salesforce Flow?

No. SuiteCRM AOW (Advanced Open Workflow) stores rule definitions as PHP-serialized objects that are not accessible via the REST or SOAP API and are not structurally compatible with Salesforce Flow. We do not migrate them as code. We deliver a written JSON inventory of every AOW workflow — module, trigger conditions, actions, and execution order — so the customer's admin can rebuild each rule as a Salesforce Flow equivalent. Role-based record assignment rules, conditional field updates, and email notifications from SuiteCRM are documented with their Salesforce Flow type recommendation (record-triggered, scheduled, or screen flow).

Can we keep SuiteCRM for some teams while moving others to Salesforce?

Yes. A phased migration where specific business units or subsidiaries move to Salesforce while others remain on SuiteCRM is a common pattern. We migrate selected record subsets (filtered by business unit fields, owner teams, or account segments) into Salesforce while leaving the SuiteCRM instance intact for the remaining teams. This requires careful scoping of the migration filter and a data ownership policy to prevent record duplication during the parallel-running period. A permanent dual-operation state is less common and adds integration maintenance overhead; most customers use it as a transition bridge of three to six months.

Do Documents and attachments migrate to Salesforce Files?

Yes, with a specific extraction step. SuiteCRM Documents store files on the server filesystem, not as database blobs. We extract the upload directory, validate file checksums, and import each file as a Salesforce ContentVersion record linked to the appropriate ContentDocument. We then attach the ContentDocument to the parent record (Account, Contact, Opportunity, or Case) via ContentDocumentLink. File metadata (document name, version, author, description) migrates as ContentVersion fields. This step is included in every SuiteCRM export plan because it is mandatory for complete record fidelity.

What happens to SuiteCRM Invoices during migration?

SuiteCRM Invoice records migrate to Salesforce, but with a clear boundary note: SuiteCRM Invoices track payment status (Paid/Unpaid) without any connection to an accounting ledger, accounts-receivable system, or general journal. We export Invoice records as-is into a custom Salesforce Invoice__c object or the standard Contract object with custom fields for invoice number, amount, and payment status. Full AR/AP reconciliation and tax filing data are sourced from the customer's accounting system, not the CRM. We flag this boundary in the scoping document and recommend that finance teams cross-reference with their accounting system post-migration rather than treating SuiteCRM Invoice records as a complete financial record.

How do we handle SuiteCRM's custom modules and Studio custom fields?

Custom modules built on SuiteCRM's SugarCRM framework are enumerated from the database vardefs during discovery. We map each to an equivalent Salesforce custom object (with __c API name), pre-create the schema in a Sandbox including all fields and lookup relationships, and import records in dependency order. Studio-defined custom fields on standard modules are handled the same way — enumerated from the vardefs, mapped to Salesforce custom fields of equivalent type, and pre-created in the destination schema before record import. We flag any SuiteCRM field types that require custom Salesforce field configuration (such as currency fields with multi-currency support or date fields with time-zone handling) during scoping.

What about SuiteCRM Campaigns and Target Lists?

SuiteCRM Campaign records map to Salesforce Campaign, and Target Lists are reconstructed as Salesforce CampaignMember records linked to the appropriate Campaign. We export each Target List as a membership set (Contact or Lead ID plus Target List ID) and recreate the memberships in Salesforce by matching contacts and leads by email during the CampaignMember import phase. Email campaign response activity (opens, clicks) migrates as Task records linked to the Campaign to preserve the response history timeline. Note that Salesforce Marketing Cloud Account Engagement (Pardot) engagement data from SuiteCRM campaign tracking does not have a direct equivalent in standard Salesforce Sales Cloud; we flag it for review and recommend a Pardot prospect migration if marketing automation continues in the Salesforce ecosystem.

Get a quote

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