Migrate from Marketing Tools Growth Marketing Platform to Salesforce Sales Cloud

The Marketing Tools platform uses a single Contact object. Salesforce uses separate Lead and Contact objects with an explicit Convert action. We apply a split rule during scoping based on the customer's use of Lifecycle Stage or acquisition source fields. Contacts with a closed-won status or account linkage map to Salesforce Contact; all others map to Salesforce Lead. The original contact record identifier preserves in a custom field src_contact_id__c for audit reconciliation.

Marketing Tools Companies map directly to Salesforce Account. The company domain name becomes the Account Website field and acts as the dedupe key during import. We export contact-company pairs together to preserve the linkage, then resolve AccountId at Contact insert time. If the source contact has no linked company, we create a placeholder Account named 'Unknown' and flag it for the customer admin to merge or reassign post-migration.

Marketing Tools Segments are rule-based with platform-specific syntax that cannot export in a transferable format. We extract segment membership per contact (the list of contacts belonging to each segment) and replicate that membership in Salesforce as Campaign Members attached to a Campaign record for each source Segment. The Campaign description carries the original segment name and rule summary for reference. The underlying rule logic must be rebuilt in Salesforce as a Flow or Audience Builder segment post-migration.

Campaign metadata from the Marketing Tools platform (name, status, start date, end date, channel, campaign type) maps to Salesforce Campaign. Campaign-level performance metrics (open rates, click rates, revenue attribution) are not available via standard export and cannot be migrated; we advise customers to export reporting snapshots from the platform's analytics dashboard before the cutover date and store them as a reference CSV.

Workflow Journeys in the Marketing Tools platform consist of triggers, branch conditions, and action steps stored in an internal automation engine not accessible via export. We cannot migrate them automatically. During discovery, we document every active journey with screenshots, trigger conditions, and action sequence, then deliver a written Flow-equivalent specification for the customer's admin or Salesforce partner to rebuild post-migration. Active journeys are flagged as high-priority rebuild items in the handoff document.

The Marketing Tools platform's custom object schema is not publicly documented in the available evidence base. Where customers report custom object usage, we attempt field-level mapping during scoping. We export the custom object records via the platform's API, attempt type-matching to Salesforce standard and custom field types, and flag any custom objects that require a custom export routine. If the destination Salesforce org is on Professional tier or above, we pre-create the custom object schema with __c API names before data import. If the source schema is completely unknown at scoping, we schedule a schema discovery sprint before migration begins.

Tags export from the Marketing Tools platform as flat key-value pairs per contact. We map them to a Salesforce custom multi-select picklist field on Contact (or Lead) or to the Label field. Tags that exceed the destination's 255-character field limit are truncated and flagged in the reconciliation report. The customer chooses between a single aggregated tag field or separate labeled fields during scoping.

File attachments associated with contacts or campaigns are not available via the documented export path. We advise customers to export attachments separately via the platform's UI export feature before the cutover date and store them in a shared drive or Salesforce Files. If the customer requires attachment migration as part of scope, we assess a custom export routine on a time-and-materials basis after the standard migration is confirmed.

Marketing Tools Owners map to Salesforce User records by email match. We extract every distinct owner referenced on Contact, Company, Campaign, and Engagement records and resolve against the Salesforce destination org's User table. Owners without a matching User go to a reconciliation queue. The customer's Salesforce admin provisions any missing Users before record import resumes.

Marketing Tools email engagements migrate to Salesforce EmailMessage records (the email content) linked to a Task record (the activity timeline entry). The WhoId on Task points to the migrated Lead or Contact; WhatId points to the related Campaign or Account. Activity ordering is preserved by setting ActivityDate to the original timestamp.

Marketing Tools call engagements map to Salesforce Task with TaskSubtype = Call. Call disposition, duration, and any recording URL transfer to custom Task fields. ActivityDate preserves the original timestamp to maintain timeline ordering in the Salesforce activity feed.

Marketing Tools meeting engagements map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendee mapping links to EventRelation records pointing at the migrated Leads, Contacts, and Users.

Marketing Tools Notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Campaign). Note body migrates as plain text. Any embedded image attachments migrate as separate ContentDocument records.

Marketing Tools task engagements map to Salesforce Task with Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving the source owner ID to Salesforce OwnerId via the User mapping table.