Migrate from Marketing 360 to Freshsales

Marketing 360 Contact records map directly to Freshsales Contact objects. The mapping preserves id, firstName, lastName, email, phone, contactName, and customerId. We resolve duplicate contacts using email as the dedupe key during import. Any Marketing 360 contacts that represent unqualified prospects (based on Status and Type taxonomy review during scoping) can optionally be routed to Freshsales Lead records if the customer's Freshsales plan includes the Leads module; this decision is made during scoping and applied as a transform rule during migration.

Marketing 360 exposes a dedicated Custom Fields API with id-value pairs per contact. We map each custom field to an equivalent Freshsales custom field under Contacts using the Freshsales Custom Fields API, preserving data types (text, number, date, picklist). Field-level mapping is documented in the migration spec before any data loads. Custom fields with no equivalent in Freshsales are flagged for field creation during schema setup.

Marketing 360 stores tag arrays with id and tag name per contact. We extract the full tag taxonomy during discovery and apply tag memberships to migrated Freshsales contacts. Tags migrate as Freshsales contact tags. The full taxonomy is preserved so that segmentation logic tied to tag membership in Marketing 360 carries forward into Freshsales reports and filters.

Marketing 360 assignees are stored as username, fullName, and email nested under Contact records. We extract every distinct assignee reference and match by email against Freshsales User records. Any assignee without a matching Freshsales User is held in a reconciliation queue; the customer provisions the missing User before record import resumes. Assigned contacts that cannot resolve a User reference are assigned to a migration service account and flagged for reassignment post-migration.

Marketing 360 uses arbitrary name-id pairs for contact Statuses and Types. We extract the full taxonomy during discovery and map each Marketing 360 Status and Type value to an equivalent Freshsales lifecycle stage (Subscriber, Lead, MQL, SQL, Opportunity, Customer). The mapping table is reviewed with the customer during scoping so that the lifecycle stage assignment reflects business intent, not just a literal field-value carryover. If the customer's Freshsales plan does not include lifecycle stages, these values migrate as a multi-select custom field.

The UXi export tool produces XML of Posts, Pages, Testimonials, and Media content but does not include layout files, theme configuration, or root-domain hosted media. We extract text content, categories, tags, and media URLs from the XML export and deliver a structured content package. Website rebuild on the destination CMS is scoped as a separate workstream. We flag the content-only export scope clearly so the customer does not expect a full-site transfer.

Marketing 360 Testimonials are exported via UXi XML as structured records with author name, content, and media URLs. We extract these as a content package for re-import into the destination CMS or as a document library. Testimonials are not CRM data and do not map to a Freshsales object; they are handled as a content migration deliverable separate from the CRM migration.

Marketing 360 automation and journey logic—trigger conditions, time delays, branch rules, and subscriber entry points—are stored in the application layer and are not exposed via the public REST API. We cannot migrate automations automatically. During discovery we document every active journey and its configuration, then deliver a manual rebuild checklist mapped to Freshsales Workflow equivalents. The customer's admin rebuilds the automations in Freshsales post-migration.

Email subscriber data and segment membership are extracted via the CRM contact export from Marketing 360. Subscriber status (subscribed, unsubscribed) migrates to the Freshsales contact record. Tag-based segment membership from Marketing 360 translates directly to Freshsales contact tags. Automated journey triggers tied to segment entry are documented as part of the automation rebuild checklist; Freshsales Workflows replace this logic post-migration.