Migrate from Inception to Salesforce Sales Cloud

Direct map. Inception contacts map to Salesforce Contacts. Salesforce requires AccountId for most operations — contacts without a primary company in Inception are attached to a default placeholder Account or flagged for manual assignment before migration commits. We validate that every contact has at least one associated company in Inception, and if a contact has multiple company affiliations, we preserve the most recently modified relationship as the primary AccountId and surface additional affiliations via Account Contact Relations in Salesforce.

Direct map. Inception company records map to Salesforce Account records. Company hierarchies (parent/child) in Inception are preserved using Salesforce's ParentId field on Account. Multi-company contacts collapse to one primary AccountId with additional companies surfaced via Account Contact Relations. We validate that parent-company references in Inception exist as separate company records before mapping the hierarchy — any orphaned parent references are flagged and resolved against your specified placeholder Account before migration commits.

Direct map. Inception deal records map to Salesforce Opportunity records. Deal stage names map to Salesforce StageName values via a value-mapping table. Close date maps directly to CloseDate. If Inception uses multiple pipelines, each pipeline requires its own Salesforce Sales Process and RecordType.

Inception's CallActivity object — storing rep calls to physicians with duration, outcome, and products discussed — maps to Salesforce Task records with Type='Call'. Call duration and outcome are preserved as custom fields (Call_Duration_Minutes__c, Call_Outcome__c) since Salesforce Task has no native duration field.

Inception Visit records (rep in-person visits with physician, date, location, and products discussed) have no Salesforce standard equivalent. We create a Salesforce custom object (Visit__c) with custom fields for Visit_Date__c, Physician_Name__c (lookup to Contact), Rep__c (lookup to User), Location__c, and Products_Discussed__c.

Inception's TargetingList object — linking rep, physician contact, targeting status, and product — requires a Salesforce custom object (TargetingList__c). We create lookup relationships to the Contact and User objects and custom pick-list fields for Targeting_Status__c (e.g., A, B, C) and Targeted_Products__c (multi-select pick-list).

Inception email engagements map to Salesforce Tasks with Type='Email'. Meetings map to Salesforce Events with original start/end times preserved. Notes map to Salesforce Notes. Original timestamps, owners, and parent-record links (ContactId, AccountId) are preserved across all three activity types. We validate that each activity record references a valid Contact or Account in Inception before mapping to Salesforce — any orphaned activity references are logged and attached to a placeholder Contact or Account as appropriate during the migration run.

Inception owner IDs (rep names linked to email addresses) are resolved by email match against Salesforce User records. Unmatched owners are flagged before migration — the team either invites the user to Salesforce first or assigns records to a fallback user. No record lands in Salesforce without a resolved OwnerId.

Inception custom contact fields (e.g., Specialization__c, Targeting_Status__c, HCP_License__c) that have no Salesforce standard equivalent are migrated as Salesforce custom fields on the Contact object using the __c suffix naming convention. Data type is preserved (pick-list, text, number) during the mapping.

Inception file attachments on records (e.g., call reports, visit summaries) are re-uploaded to Salesforce Files linked to the parent Contact, Account, or custom object record. Salesforce's 25MB per-file size limit applies — larger files are flagged for splitting or alternative storage before migration.