Migrate your Zoho Marketing Plus data

Standard contact records with name, email, phone, and custom fields. We map Contact fields 1:1 via the Marketing Automation API or CSV import, preserving all custom field data. Note that each plan tier bundles contact quotas (1,000 per marketer seat) that must be pre-allocated before import.

Campaigns are the central execution unit covering email, social, webinar, and event channels. We export campaign metadata, audience lists, and performance metrics as structured JSON and CSV for reconstruction in the destination platform.

Multi-step engagement journeys built with visual editors. Journey steps, triggers, conditions, and delays are exportable as JSON configuration but require field mapping because destination platforms use different automation terminology and action types.

Landing pages created in Zoho LandingPage are exportable as HTML and asset bundles. We preserve page structure and form fields but re-mapping to equivalent page builders in the destination is required due to varying widget models.

Zoho Survey objects including question types, answer options, logic branches, and response data are migrated. Survey logic (skip conditions, piping, branching) requires manual field mapping against destination survey platforms.

Events cover registrations, session data, speaker info, and attendee records. We export event metadata and attendee lists, but event-specific settings (room capacity, ticketing tiers, session scheduling) need destination-specific configuration.

Webinar attendee records, registration status, and attendance data are migrated. Zoho Webinar-specific identifiers and session links are stripped and replaced with equivalent destination webinar platform references.

Scheduled posts and social media content are exported as post metadata (text, images, schedule, channel targets). Post-level analytics are preserved separately. Full social listening/mentions data is not exported via standard API and must be reconstructed.

Brand asset libraries (documents, presentations, PDFs, videos) stored in Zoho's collateral management are exportable as file bundles. We preserve folder hierarchy and naming conventions; destination platform asset library structure must be recreated.

Visitor tracking data and session records are tied to Zoho PageSense. This is primarily analytics data rather than contact records. Visitor quotas (10,000 per marketer seat) must be allocated in the destination platform separately.

Custom fields created via the Marketing Automation API v1 are fully supported for migration. Field types include text, integer, phone, date, picklist, email, checkbox, multiselect, datetime, decimal, percent, and URL. We create matching custom fields in the destination before importing records.

User accounts with roles (admin, marketer, custom) and team assignments are migrated as user metadata. Destination platforms map roles differently; we preserve role names as a custom property and apply the nearest equivalent in the target system.

Campaign performance reports and cross-channel analytics are exported as CSV or XLSX. We preserve report structure and historical data points, but dashboard visualisations cannot be transferred directly and must be rebuilt in the destination BI tool.

Multi-brand management is a native Zoho Marketing Plus feature. Brand configuration including sub-brands, brand-specific assets, and brand-level campaign scoping migrates cleanly as structured data.