Migrate from Spark CRM to Salesforce Sales Cloud

Spark contacts map 1:1 to Salesforce Contacts. The AccountId field is required on Salesforce Contacts, so Spark contacts without a primary company link to a designated 'Unassigned' Account record. Email, phone, title, and address fields migrate directly with field names adapted to Salesforce PascalCase conventions.

Spark companies map to Salesforce Accounts. Company name becomes Account.Name, domain becomes Website, industry values are mapped via value-mapping against Salesforce's standard industry pick-list. Parent-company hierarchies in Spark map to the Account.ParentId field; circular references are flagged before migration commits.

Spark deals map to Salesforce Opportunities. The deal name becomes Opportunity.Name, amount maps directly, close date maps to CloseDate, and owner resolves via email match to Salesforce User records. Pipeline assignment requires mapping to a Salesforce Sales Process tied to a RecordTypeId.

Each Spark pipeline becomes a Salesforce Record Type with an associated Sales Process. The record type defines which stage pick-list values are available per deal category. We deliver a record-type setup plan specifying the page layout assignments, profile access, and stage pick-list values for each pipeline before data migration runs.

Stage names are mapped value-by-value from Spark to Salesforce. Each stage gets a probability value and forecast category assigned based on Salesforce's stage-history model. Stage-entered timestamps are preserved as custom datetime fields (Stage_Entered_Date__c) for reporting continuity on the Opportunity record.

Spark call logs migrate as Salesforce Tasks with Task.Type = 'Call'. Original timestamps (CreatedDate equivalent), subject, and owner links are preserved. The Task.WhatId links to the parent Account or Opportunity record from the Spark activity association. Call duration and outcome fields map to CallDurationInSeconds and CallType respectively. If Spark recorded a disposition code, it is stored in a custom field on the Task.

Spark email activities migrate as Salesforce Tasks with Task.Type = 'Email'. Subject line and body content transfer as Task.Subject and Task.Description. Owner resolution follows the same email-match logic used for all owner fields. Inline attachments download and re-upload as Salesforce Files linked to the Task.

Spark meetings migrate as Salesforce Events. Start time, end time, subject, and location map to Event.StartDateTime, EndDateTime, Subject, and Location respectively. The Event.WhatId links to the parent Account or Opportunity record. Owner assignment follows email-based user resolution. Meeting agenda and attendee information are stored in custom fields if present in Spark. Recurring meetings are expanded into individual Event records.

Spark notes migrate to Salesforce Notes (not the legacy Note object). Title, body, and created date transfer. Rich-text formatting is preserved where the source format is compatible. Notes are linked to their parent Contact, Account, or Opportunity record via the ParentId field.

Spark file attachments re-upload to Salesforce Files. Each file gets a ContentDocument record with a ContentVersion. Files are linked to their parent record via ContentDocumentLink. Salesforce's 25MB per-file limit applies; files exceeding this are flagged for manual handling before the migration runs.

Spark contact custom fields become Salesforce custom fields on the Contact object with the __c suffix. Field type mapping follows type-aware conversion: text fields become Text(255), number fields become Number, pick-list fields become Picklist with value-mapping. All custom fields are created in the target org before the migration phase begins.

Spark deal custom fields map to custom fields on the Opportunity object. Fields that hold monetary values use Currency data type with appropriate decimal precision. Priority or status fields become custom Picklist fields with value-mapping against the destination pick-list values defined in the Salesforce org.

Spark contact-deal associations map to Salesforce OpportunityContactRole junction records. Each association creates an OpportunityContactRole entry with the ContactId, OpportunityId, and Role fields. If Spark stored a role label that has no Salesforce standard Role value, we map it to 'Other' and preserve the original label in a custom field on the junction record.

Spark owner records are resolved against Salesforce Users by email address. Records where no matching Salesforce User exists are flagged before migration; the team assigns them to a fallback owner or invites the user to Salesforce first. No record lands without a resolved OwnerId.