Migrate from Sales Journey to Salesforce Sales Cloud

Sales Journey Contact records with a lifecycle stage or status property indicating an unqualified prospect map to Salesforce Lead. Contacts with a qualified status or associated deal activity map to Salesforce Contact tied to a Salesforce Account. We derive the split at migration time using the source lifecycle or status property, and preserve the original stage in a custom field sj_original_lifecycle__c on both Lead and Contact for audit and reporting continuity. Account-Contact hierarchy is resolved during the Account import phase so that Contact insert satisfies the required AccountId lookup.

Sales Journey Company records map directly to Salesforce Account. Standard address fields, industry, employee count, and annual revenue migrate to their Salesforce Account equivalents. Company is imported first in the dependency sequence so that the AccountId lookup is available when Contact records are inserted. The Company name becomes the Account Name; domain or website becomes the Account Website field for dedupe validation.

Sales Journey Deal records map to Salesforce Opportunity. The Deal name becomes Opportunity Name, stage maps to Salesforce StageName via a stage mapping table built during scoping, close date maps to CloseDate, and Deal value maps to Amount. Owner assignment is preserved as OwnerId via the User cross-reference table.

Each Sales Journey pipeline stage becomes a Salesforce StageName value in a Sales Process. We configure stage probability percentages to match the original Sales Journey stage weights, rounding to the nearest integer allowed by Salesforce. Stage mapping is written to the scoping document before any data moves so the customer can validate that stage semantics match their current sales process.

If the customer's Sales Journey instance uses a distinct Lead object (separate from Contact) for pre-qualified prospects, those records migrate to Salesforce Lead with LeadSource, Status, and any custom fields preserved. Lead conversion history (if exposed in the export) is documented for the customer's admin to recreate in Salesforce by converting the corresponding Leads after migration.

Owner assignment on all Sales Journey records exports as a user reference (email or ID depending on export format). We map source owner IDs to Salesforce User records by email match. Any owner without a matching Salesforce User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId is resolved for Contacts, Companies, Deals, and Activities before each import phase begins.

Sales Journey email engagement records migrate to Salesforce EmailMessage (the email content) linked to a Task (the activity timeline entry). The WhoId on Task points to the migrated Lead or Contact; the WhatId points to the related Opportunity or Account. ActivityDate is set to the original Sales Journey timestamp to preserve timeline ordering. If engagement data cannot be extracted cleanly as structured records, we flag the gap in the scoping report and recommend manual export or acceptance of the data loss.

Sales Journey call engagement records map to Salesforce Task with TaskSubtype = Call. Call disposition, duration, and any notes field transfer to custom Task fields. ActivityDate is set to the original Sales Journey timestamp to preserve sequence. We validate that TaskSubtype field is available in the destination Salesforce edition before configuring this mapping.

Sales Journey meeting engagement records map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendee resolution uses the User cross-reference for internal attendees and the Contact or Lead cross-reference for external attendees. If Sales Journey meeting records include attendee data that cannot be exported, we document the limitation in the scoping report.

Sales Journey Notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Opportunity). Note body migrates as plain text; rich text formatting is simplified to plain text unless the export format preserves HTML. File attachments associated with Notes migrate as separate ContentDocument records attached via ContentDocumentLink.

Sales Journey task records (standalone tasks, not engagements) map to Salesforce Task with Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving the source owner reference to Salesforce OwnerId via the User cross-reference table. Completed status maps to the Salesforce Task Status values that the customer's org has configured.

If Sales Journey supports custom fields on standard objects, we audit every custom field during discovery by walking the customer through every workflow and form they use. Custom field types, picklist values, and any validation rules require explicit mapping to Salesforce field types. We pre-create the destination schema in a Salesforce Sandbox before production migration. Any custom field discovered during export that was not identified during discovery is added to the mapping table and the customer is notified before migration resumes.