Migrate from Marketing 360 to Salesforce Sales Cloud

Marketing 360 Contacts map to Salesforce Lead for prospects and to Contact attached to an Account for customers. We define the split rule during scoping using Marketing 360's lifecycle stage properties (subscriber, lead, MQL, SQL, customer, evangelist) mapped to Salesforce's Lead Status and Account-Customer flags. We preserve the original Marketing 360 lifecycle stage in a custom field m360_original_lifecycle__c on both Lead and Contact for audit and reporting continuity.

Marketing 360 Company records map to Salesforce Account. The Company domain becomes the Account Website field and serves as the dedupe key during import. Account is created before any Contact import so the Lookup relationship is satisfied at Contact insert. Companies without an organizationId receive a placeholder Account for reconciliation.

Marketing 360 exposes a dedicated Custom Fields API with id-value pairs per contact. We map each custom field to a Salesforce custom field of matching data type (text, number, date, checkbox, picklist). The destination custom field schema is deployed to Sandbox before migration for validation. Custom field API names preserve the m360 prefix for traceability.

Marketing 360 tag arrays (tag id and tag name) are extracted in full taxonomy form. Tags used for contact segmentation migrate to a Salesforce multi-select picklist if the tag count stays within the 500-value limit, or to a custom text field with semicolon delimiters if the taxonomy exceeds picklist capacity. The customer chooses tag strategy during scoping.

Marketing 360 assignees store username, fullName, and email nested under contact records. We resolve assignees by email match against the Salesforce User table. Any Marketing 360 assignee without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Marketing 360 uses arbitrary name-id pairs for contact Statuses and Types. We extract the full taxonomy from the API and map these to Salesforce picklist fields (m360_contact_status__c, m360_contact_type__c) with values preserved exactly. If the destination org already has equivalent picklists, we map values during scoping rather than creating new fields.

Marketing 360 Deals map to Salesforce Opportunity. The Deal pipeline maps to a Salesforce Record Type and Sales Process that we configure before migration. Deal stage maps to Opportunity StageName; closed-lost and closed-won reasons map to Loss Reason and Win Reason fields. Deals without an associated Company create a placeholder Account for the Opportunity to attach to.

The UXi export tool produces XML containing Posts and Pages content (title, body text, categories, tags, media references). Layout files and theme configuration are not included. We extract text content, category assignments, and accessible media URLs from the XML and import as Salesforce Content records or Notes attached to Accounts. Website rebuild scope is documented as a separate line item.

Testimonials export from UXi XML as structured records with author name, content body, and media URLs. We import Testimonials as Salesforce Note records (with rich text body) attached to the related Account or Contact, or as Content records if the testimonials include media assets. The testimonial author name maps to the Note title field.

The UXi export includes references to uploaded media files but does not bundle root-domain hosted assets. We download accessible media during export where the URLs are publicly reachable and re-upload to Salesforce as ContentDocument records attached to the relevant Account or Contact. Media assets that require authentication or are hosted exclusively on the Marketing 360 domain are flagged for manual re-upload.

Email subscriber data and segment membership extract from the CRM contact export. Marketing 360 email opt-in and opt-out preferences map to Salesforce HasOptedOutOfEmail and EmailOptOut fields. Segment membership that drives journey entry is preserved in a custom field m360_segments__c for the customer's admin to use in rebuilding marketing automation in Salesforce or a separate marketing platform.

Marketing 360 automation and journey logic (trigger conditions, time delays, branch rules, subscriber entry points) are stored in the application layer and not exposed via the public REST API. We cannot migrate automated workflows automatically. During scoping we document all active journeys with their trigger, conditions, actions, and delays, and we deliver a manual rebuild checklist mapped to equivalent Salesforce Flow triggers and actions.

Marketing 360 bundles its own payment processing layer with card-present and card-not-present fee structures, hardware costs, chargeback fees, and $129/month POS license per location. These do not live in the CRM export and cannot migrate. We separate payment processor reconfiguration as a distinct workstream and flag the fee differential for the customer's finance team to evaluate third-party payment integrations available on Salesforce AppExchange.