Migrate from Simply CRM to Salesforce Sales Cloud

Simply CRM contacts with no associated deals or early-stage associations route to Salesforce Lead. Contacts attached to closed or active deals route to Salesforce Contact. The split preserves the source contact record ID in Source_System_ID__c for traceability, enabling downstream cross-reference and delta-sync validation against the original Simply CRM export. This contact-to-lead routing logic is configurable per deal stage name, allowing your admin to tune the threshold based on sales process definitions.

Simply CRM company name, domain, industry, employee count, and annual revenue map directly to Salesforce Account fields. Parent-company relationships in Simply CRM map to Account.ParentId — parent accounts must migrate first to avoid orphaned child records. Circular parent-child references are detected during the pre-migration audit and flagged for admin resolution before the full migration batch commits to Salesforce.

Simply CRM deals become Salesforce Opportunities. The deal name maps to Opportunity.Name, amount to Amount, close date to CloseDate, and owner to OwnerId via email resolution. Pipeline stages map to Opportunity Stage values per Salesforce Record Type, with probability and forecast category reapplied from Salesforce-side stage configuration. The Simply CRM deal ID is stored in Source_System_ID__c for audit traceability.

Each Simply CRM pipeline maps to a Salesforce Record Type so stage pick-list values are scoped correctly per business unit. The Salesforce Sales Process ties to the Record Type, controlling which stage values are available. Multiple pipelines in Simply CRM result in multiple record types in Salesforce.

Simply CRM deal stage names map value-by-value to Salesforce Opportunity Stage pick-list values. Stage probability and forecast category are reapplied from Salesforce-side configuration. Stage-entered timestamps from Simply CRM are preserved as custom datetime fields for reporting continuity. Any stage names without a direct Salesforce equivalent are flagged for explicit mapping before the migration run.

Simply CRM tasks (calls, emails, follow-ups) migrate to Salesforce Task records with Type='Call' or Type='Email' preserved from the source activity type. Original timestamps, owners, and parent-record links (WhoId, WhatId) are maintained through the mapping. Tasks without a resolvable parent record (deleted source contacts or companies) are linked to a fallback WhatId or flagged for manual review.

Simply CRM calendar events map to Salesforce Events with original start/end times, subject, and location preserved. Recurring events expand to individual Event records per occurrence. Parent-record links (WhoId, WhatId) resolve to Salesforce Lead or Contact IDs post-migration. Events referencing deleted parent records are held from the migration batch pending admin decision on whether to orphan or discard.

Simply CRM notes migrate to Salesforce Notes (modern Notes object, not legacy Note). Rich-text formatting is preserved through the migration. Notes attach to parent records via Salesforce's ContentDocumentLink mechanism. Notes exceeding Salesforce's 32KB body limit are flagged — these may be split into multiple Notes or stored as attachments if splitting is not feasible.

Simply CRM file attachments download and re-upload to Salesforce Files (ContentDocument/ContentVersion). File size limits apply — Salesforce defaults to 25MB per file. Files are linked to parent records via ContentDocumentLink. Inline images in notes extract and rehost as separate content.

Simply CRM custom fields (cstm_ prefix in database) map to Salesforce custom fields with the __c suffix. Custom pick-list fields require value-by-value mapping in Salesforce. Custom date, number, currency, and text fields map by data type. The Salesforce admin creates fields before migration validation runs.

Simply CRM assigned_user_id values resolve to Salesforce User IDs by email address. Users present in Simply CRM but not in Salesforce are flagged before migration — either invited to Salesforce first or assigned to a fallback user. This prevents records landing with null OwnerId.

Simply CRM supports N:1 contact-to-company associations natively. Salesforce supports a primary AccountId on Contact plus Account Contact Relations for additional accounts. The most-recently-modified company becomes the primary AccountId; others migrate as Account Contact Relations with Roles if Simply CRM association labels exist.

Simply CRM campaign records migrate to Salesforce Campaign with name, type, status, start/end dates, and budgeted cost preserved. Campaign members link to Salesforce Leads or Contacts based on the contact's migration destination. Note: marketing automation logic (drip sequences, enrollment criteria) does not migrate.

If Simply CRM project management extensions are in use, custom object migration applies. Projects map to a Salesforce custom object (Project__c) with Project Tasks as a related list. We assess the specific schema from the source export before mapping. Standard Salesforce Tasks cannot fully replicate project management without custom object design.