Migrate from Pure Chart to Salesforce Sales Cloud

Pure Chart contacts with lifecycle_stage in 'subscriber', 'lead', 'MQL', or 'SQL' route to Salesforce Lead. Contacts with lifecycle_stage in 'customer' or 'evangelist' land as Salesforce Contact. Split happens at migration time based on source lifecycle value; original stage preserved as Lifecycle_Stage__c custom field.

Direct map. Pure Chart company hierarchies (parent/child) use Salesforce's ParentId field. Multi-company contacts in Pure Chart (N:N model) collapse to one primary AccountId per contact with additional companies surfaced as Account Contact Relationships on the contact record. During migration, we preserve the parent-child hierarchy so reporting by region or business unit remains intact.

Direct map. Pure Chart deal pipelines map to Salesforce Sales Processes keyed by RecordTypeId. Each Pure Chart pipeline = one Salesforce record type. Pipeline stage names map to Opportunity StageName values scoped per record type with probability and forecast category reapplied.

Pure Chart's pipeline object becomes a Salesforce Sales Process. Each pipeline requires its own RecordTypeId in Salesforce so stage pick-list values are correctly scoped per deal type. Your admin creates record types before the migration; FlitStack delivers a schema setup plan specifying which record types are needed.

Stage names map value-by-value per record type. Stage probability percentages and forecast category assignments reapplied from Salesforce-side configuration. HubSpot stage-entered timestamps preserved as custom datetime fields (Stage_Entered_Date__c) on the Opportunity for historical continuity. If your Pure Chart pipeline includes custom stage names not present in Salesforce, we create matching StageName values and assign probabilities aligned with your historical win rates.

Salesforce has no native lifecycle_stage equivalent. We create Lifecycle_Stage__c as a custom pick-list field on both Lead and Contact with HubSpot's exact values preserved. Stage-change timestamps preserved as Lifecycle_Stage_Updated__c custom datetime field for audit continuity. You can use Lifecycle_Stage__c in list views, reports, and flow criteria to trigger outreach based on the prospect's stage without custom joins.

Pure Chart call activities migrate as Salesforce Tasks with Type='Call'. Original call duration, outcome, owner, and timestamp preserved. Task links to parent Contact or Lead via WhatId/WhoId depending on whether the contact routed to Lead or Contact. If the call outcome includes custom disposition codes, we map those to Salesforce CallDisposition values or create a custom field to retain the original categorization.

Pure Chart email activities migrate as Salesforce Tasks with Type='Email'. Email subject, body text, and timestamp preserved. Inline attachments require separate file handling — downloaded from Pure Chart and re-uploaded to Salesforce Files with parent record link. For emails with large attachments, we chunk the upload to stay within Salesforce's 25MB per‑file limit and log any exceeding files for manual review.

Pure Chart meetings migrate as Salesforce Events with original start time, end time, subject, location, and attendee list preserved. Meeting body notes map to Event Description. Event links to parent Contact or Lead via WhoId. If the meeting includes resources such as rooms or equipment, we store those details in the Event Location field and add a custom field for resource references.

Pure Chart notes migrate as Salesforce Notes (rich-text body preserved). Notes attach to the appropriate parent record — Contact, Lead, Account, or Opportunity — based on the source note's associated entity. If a note references multiple entities, we link it to the primary entity and add a custom multi-select field to list secondary associations for downstream reporting.

Pure Chart custom objects map 1:1 to Salesforce custom objects. Custom object API names get the __c suffix. Custom object associations that use Pure Chart's N:N model require Salesforce junction objects — the migration plan surfaces these before the run commits.

Pure Chart file attachments on records are downloaded and re-uploaded to Salesforce Files. File size limits apply (Salesforce default 25MB per file). Files link to the parent record via ContentDocumentLink. Inline images in notes are extracted and re-hosted as Salesforce Files.

Pure Chart owner IDs resolved by email match against Salesforce User records. Unmatched owners are flagged before migration commits — your team either provisions Salesforce users first or assigns records to a fallback owner. No record lands without a valid Salesforce OwnerId.

Pure Chart association labels (Decision Maker, Champion, Influencer) that connect contacts to deals map to Salesforce Opportunity Contact Roles for standard roles. Non-standard labels require a custom junction object — your admin chooses whether to recreate every label or collapse into fewer categories.