Migrate your Sales Journey data

Contacts is the core person record in Sales Journey. We export all standard contact fields including name, email, phone, and company association. Field mapping to destination CRM contact objects is straightforward since the schema aligns with industry-standard CRM conventions.

Company records export cleanly with standard address, industry, and size fields. We preserve the relationship between companies and their associated contacts during migration and re-establish the link in the destination CRM.

Deal records export with stage, value, and owner assignment. Pipeline stage names vary between source and destination CRMs so we create a stage mapping table during scoping. Close date and probability fields require value-level alignment where destination systems use enumerated stages.

Lead records may use a different lifecycle model than destination CRMs. We export Leads with their current status and conversion history preserved, then map to the appropriate lifecycle stage in the destination system—Contact, MQL, or Opportunity—based on the customer's workflow.

Activity records including emails, calls, and notes export with timestamps and owner assignment. Engagement scoring or behavioral data may not map 1:1; we flag which activity attributes are preserved and note any that require manual recreation in the destination.

If Sales Journey supports custom fields on standard objects, we audit them during the discovery phase. Custom field types, validation rules, and picklist values require explicit mapping to destination field definitions. Fields with unsupported data types are flagged for manual remediation.

Pipeline configuration including stage names, stage order, and win/loss criteria exports as metadata. Stage-level probability and forecasting settings require reconfiguration in the destination CRM since each platform has its own pipeline modeling approach.

Owner assignment on records exports as a user reference. We map source user IDs to destination user IDs using a cross-reference table. If users do not yet exist in the destination CRM, we flag them for creation or reassignment before migration.

File attachments stored within records may require a separate export step if they are not included in the standard record export. We identify attachment storage location and size during scoping and include them in the migration package with record-level associations preserved.

Tagging taxonomy exports as a flat list per record. Where destination CRMs use a different tagging or labeling model, we map tags to equivalent labels, segments, or custom properties based on the customer's use case.