Migrate from Zoho Marketing Plus to Twenty CRM

Zoho Marketing Plus Contacts migrate to Twenty Contact records via the Contacts API. All standard fields (name, email, phone, address) map 1:1. Custom contact fields created via the Marketing Automation API v1 (text, integer, phone, date, picklist, multiselect, checkbox, email, decimal, URL, text area, anniversary) map to Twenty's custom field schema by type. Zoho merge tags embedded in field values are stripped during transform and flagged in the handoff document. Contact Owner maps from Zoho Owner to Twenty User by email lookup; unresolved owners go to a reconciliation queue for admin provisioning before record import.

Zoho Marketing Plus Companies migrate to Twenty Company records. The Zoho company domain becomes the Website field and serves as the dedupe key during import. Company custom fields map to Twenty Company custom fields by type. Company is created before any Contact import so that the parent lookup is satisfied at insert time.

Zoho Campaigns migrate to Twenty Opportunity records. Campaign name becomes Opportunity name; campaign status maps to Twenty pipeline stage; campaign start and end dates migrate as custom date fields on the Opportunity. If the customer has multiple campaigns per contact, these may also be tracked as Opportunity records with a campaign_type custom field for segmentation. Campaign metadata (audience size, channel, performance metrics) migrates as structured JSON in a campaign_metadata__c text field.

Zoho allows up to 150 custom fields (75 text maximum) per Marketing Automation account. All field types map to equivalent Twenty custom field types: text to TEXT, integer to NUMBER, date to DATE, picklist to ENUM, multiselect to ENUM_MULTI, checkbox to BOOLEAN, phone to PHONE, email to EMAIL, decimal to DECIMAL, URL to URL, text area to TEXTAREA. Field order and section placement are preserved in the migration schema document. Fields exceeding Twenty's type constraints are flagged for admin review before import.

Zoho Journeys (multi-step automation workflows with triggers, conditions, delays, and CRM actions) are exported as JSON configuration metadata. We preserve trigger types, condition branches, action steps, and delay configurations as a structured JSON file. Journeys do not migrate as executable code because Twenty CRM has no native automation engine. The JSON inventory is delivered to the customer's admin team with a recommendation for rebuilding in their chosen automation tool (Make, Zapier, n8n, or a native CRM workflow tool).

Zoho Landing Pages export as HTML and asset bundles preserving page structure and form field definitions. The HTML and form field inventory is delivered as a file bundle. Re-mapping to equivalent page builders (Carrd, Webflow, WordPress, Typeform) is required post-migration and falls outside the migration scope. Form field definitions are preserved to aid reconstruction.

Zoho Survey objects — question types, answer options, logic branches, skip conditions, and response data — are exported as structured JSON. Survey logic (branching, piping, skip conditions) requires manual field mapping against the customer's chosen replacement survey tool. Response data migrates as Contact records with survey_response__c and survey_score__c custom fields where applicable.

Zoho Events (registrations, session data, speaker info, attendee lists) export as structured metadata. Room capacity, ticketing tiers, session scheduling, and registration limits are preserved in the inventory JSON. Events do not have a native Twenty CRM equivalent; the inventory document is delivered for the customer to configure in their chosen event platform post-migration. Registrant and attendee names and emails migrate as Contact records with an event_name__c custom field.

Zoho Webinar attendee records, registration status, and attendance data migrate as Contact records with webinar_registration_status__c and webinar_name__c custom fields. Zoho Webinar-specific identifiers and session link URLs are stripped from the import and replaced with a flag to reconnect to the customer's chosen webinar platform (Zoom, Loom, or equivalent) post-migration. Attendance records migrate as Note records attached to the Contact.

Zoho Social Posts (text, images, schedule, channel targets) export as post metadata JSON including post copy, image asset references, scheduling timestamps, and channel targets. Analytics data migrates as structured CSV. Full social listening and mentions data is not migratable as it is platform-hosted. The social post metadata JSON is delivered for the customer to schedule via their chosen social management tool (Buffer, Sprout Social, or equivalent) post-migration.

Brand asset libraries (documents, presentations, PDFs, videos) stored in Zoho's collateral management export as file bundles with folder hierarchy and naming conventions preserved. Destination platform does not have native asset management; files are delivered as a structured zip archive organized by brand folder for re-upload to the customer's chosen DAM tool (Front, Bynder, or equivalent) post-migration.

Zoho PageSense visitor tracking data and session records are primarily analytics data rather than contact records. Visitor records tied to known email addresses migrate as Contact records with a pageviews__c counter field. Anonymous visitor data is inventoried as a CSV for reconnection to the customer's chosen analytics or tracking platform (Google Analytics, Mixpanel, or equivalent) post-migration. Zoho visitor quotas (10,000 per marketer seat) are not relevant in Twenty CRM which has no per-visitor billing.