Migrate from Marketing 360 to Zoho CRM

Marketing 360 Contacts map directly to Zoho CRM Leads. The Marketing 360 API exposes id, firstName, lastName, email, phone, contactName, customerId, and organizationId. We map firstName and lastName to Zoho Lead fields First_Name and Last_Name, email to Email, phone to Phone, and customerId to a custom field m360_customer_id__c as a dedupe and audit reference. If Marketing 360 records include a lifecycle stage property, we preserve it in a custom field original_lifecycle__c.

Marketing 360 exposes a dedicated Custom Fields API with id-value pairs per contact. During migration we create matching custom fields in Zoho CRM (Setup > Modules and Fields > Leads > add custom field) using type-mapped Zoho field types: text fields for strings, numeric fields for integers and decimals, date fields for date values, and checkbox fields for boolean flags. Zoho allows up to 150 custom fields per module depending on edition. We create all custom fields in Zoho before importing contact records so that values insert directly rather than requiring post-migration field creation.

Marketing 360 contact records carry tag arrays with id and tag name. Zoho CRM uses a Tag field as a multi-select picklist on each module, with a maximum of 10 tags per record and 25 characters per tag. For records with more than 10 tags we split into two fields: primary_tags (first 10 tags, up to 25 characters each) and secondary_tags_notes (remaining tags stored in a Notes field), both flagged in the mapping spec. Tags used for segmentation logic are extracted as a full taxonomy list for the customer to restructure in Zoho as needed.

Marketing 360 stores assignees as nested objects with username, fullName, and email per contact record. We resolve assignees by email match against the Zoho CRM User table during migration. Any Marketing 360 assignee without a matching Zoho User record is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Unresolved assignees default to the Zoho admin user with a note added to the record for manual follow-up.

Marketing 360 uses arbitrary name/id pairs for contact Statuses and Types. We extract the full taxonomy from the Marketing 360 API and map each value to a corresponding Zoho Lead Status or a custom picklist field lead_type__c, applying the same label names to preserve readability. Values that do not map to a Zoho standard picklist are created as custom picklist values during schema setup before the import phase.

The UXi export tool produces XML containing Posts, Pages, Testimonials, and Media references. Layout files and theme assets are not included in the export. We extract text content, categories, tags, and media URLs from the XML and import them as Zoho Notes attached to the corresponding Lead record, or into Zoho Wiki if the customer licenses Zoho One. We flag this as a content-only migration with a rebuild scope line item for the customer's web team. Root-domain media assets hosted on Marketing 360 servers are downloaded during export where accessible and re-uploaded to the destination CMS.

Marketing 360 Testimonials export via the UXi XML as structured records with author name, content, and media URLs. We import testimonials as Zoho Notes attached to the relevant Contact or Lead record, or as records in a custom Testimonials module if the customer requires structured testimonial data. Author attribution and content text migrate fully; media attachments migrate where URLs are externally accessible.

Marketing 360 automations and journey logic—trigger conditions, time delays, branch rules, and subscriber entry points—are not exposed via the public REST API. We do not migrate automation journeys as executable code. During scoping we document every active Marketing 360 journey (journey name, trigger type, steps, actions, and any active/enrolled contacts) and deliver a written rebuild checklist mapped to Zoho CRM Workflow Rules, Blueprints, or Macros equivalents. The customer's admin rebuilds these in Zoho post-migration.

Email subscriber data and segment membership are extracted via the CRM contact export. Automated journey triggers tied to segment entry require review and manual reconfiguration in Zoho Campaigns or Zoho Marketing Automation if the customer licenses those products. Subscriber opt-in status migrates to a custom field email_consent__c on the Lead record for use in Zoho email delivery settings.

Marketing 360 bundles its own payment processing layer with card-present and card-not-present fee structures, hardware costs, chargeback fees, and payout fees. These do not live in the CRM data model and cannot be extracted via the Marketing 360 API. We separate payment reconfiguration as a distinct workstream in the migration plan and flag the fee differential for the customer's finance team. The customer selects a replacement payment processor (Stripe, Square, Zoho Books integrations, or another provider) and reconfigures payment settings independently of the CRM migration.