Migrate from SuiteCRM to Salesforce Sales Cloud

SuiteCRM Accounts map directly to Salesforce Account. 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.

SuiteCRM Contacts map to Salesforce Contact. 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.

SuiteCRM Leads map to Salesforce Lead. 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.

SuiteCRM Opportunities map to Salesforce Opportunity. 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.

SuiteCRM Products catalogue maps to Salesforce Product2 records with Standard Price Book entries created during import. ProductCode, description, and pricing migrate. Products must be imported before Quotes and Line Items to satisfy the Pricebook2 reference on child records.

SuiteCRM Quotes map to Salesforce Quote, which is available from the Professional tier. 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.

SuiteCRM Contracts module maps to Salesforce Contract. Start date, end date, renewal status, and Account linkage migrate as standard fields. Contract record type and status values are pre-configured in Salesforce before migration so that renewal flags are preserved.

SuiteCRM Invoice records do not represent a full accounting ledger — they track payment status without AR/AP or general journal entries. We export Invoice records as-is into a Salesforce custom object (Invoice__c) or the standard Contract object with custom fields for invoice number, amount, status, and payment date. Full accounting reconciliation requires the customer's ERP as the source of truth; we flag this boundary clearly in the scoping document.

SuiteCRM Cases (Bugs module) map to Salesforce Case. Case status, priority, description, and related Contact or Account link migrate. If Service Cloud is active in the destination org, Case Record Types and Status values are pre-configured. Related activity notes and history migrate as Task and Note records linked to the Case.

SuiteCRM Campaign records map to Salesforce Campaign. Campaign type, status, start and end dates, budgeted cost, and expected revenue migrate. Target Lists migrate as Campaign Member lists linked via CampaignMember records, with Contact or Lead matched by email during the import phase.

SuiteCRM Target Lists store membership as a junction between Contacts, Leads, and Prospects. We export Target List memberships as a Contact-to-TargetList junction table, then reconstruct them as Salesforce CampaignMember records during import. Each Target List becomes a separate Campaign with its target members added as CampaignMembers.

SuiteCRM Documents store files on the server filesystem (/upload/ directory) with metadata records in the database. We extract both — file blobs with integrity checksums and the corresponding metadata records — and import into Salesforce as ContentVersion (file blob) and ContentDocument (metadata). File permissions must be preserved during extraction or files become inaccessible. We validate checksums after extraction and before Salesforce upload.

SuiteCRM Users map to the owner field on all records. We export the Users table including usernames and email addresses. Salesforce Users must be provisioned by the customer's admin before record import begins. We match by email address and hold records with unmatched owners in a reconciliation queue until User provisioning is complete.

SuiteCRM Studio custom fields are stored in extended database tables with a naming convention appended to the module name. We enumerate all Studio-defined fields during discovery, map each to a Salesforce custom field of equivalent type (text, date, picklist, checkbox, number, currency), and pre-create the Salesforce schema in a Sandbox before production migration. Picklist values must match exactly between systems or import will reject records.

Custom modules built on SuiteCRM's SugarCRM framework map to Salesforce custom objects with __c API names. We enumerate the custom module schema from the SuiteCRM database vardefs, pre-create the equivalent Salesforce custom object including all fields and lookup relationships, then import records in dependency order. Custom modules with lookups to standard objects (Account, Contact) are imported after those standard objects are present in Salesforce.