Migrate from Zoho Marketing Plus to Freshsales

Zoho Marketing Plus Contacts map directly to Freshsales Contacts. We extract contact records via the Zoho Marketing Automation API or CSV export, preserving standard fields (First_Name, Last_Name, Email, Phone) and all custom Contact fields. Custom fields migrate 1:1 when the exact field name exists in Freshsales Admin Settings under the Contacts module; the customer must pre-create custom fields with matching names before migration so Freshsales auto-maps them. Multi-select picklists from Zoho map to Freshsales multi-select fields. The Zoho Contact owner (marketer) maps to Freshsales User via email match.

Zoho Marketing Plus does not have a dedicated Company object as a top-level record type, but mailing lists and contact records often contain company name as a property. We extract distinct company_name values from Contacts and create Freshsales Account records. The Account Name becomes the Freshsales Account name, and we link the original Contact records via the Account-Contact relationship. Company address fields from Zoho map to Freshsales Account address fields. This is a 1:N enrichment pattern: multiple Zoho Contacts from the same company consolidate into one Freshsales Account with multiple Contacts linked.

Zoho Marketing Plus Campaigns (the campaign workspace covering email, social, webinar, and event activities) do not have a direct Freshsales equivalent because Freshsales does not have a campaign management module. We extract campaign metadata (campaign name, status, start date, description) as a structured JSON bundle and create a Freshsales Deal (Potential) record that captures the campaign as a sales-typed record. Campaign audience lists migrate as Freshsales Contacts or as a Contact List in Freshsales (a grouping without a native Freshsales CRM object, stored as a custom field or tag). Campaign performance metrics (open rate, click rate, sends) are preserved in the JSON bundle for reference and cannot be rendered inside Freshsales natively.

Zoho Marketing Plus Journeys (multi-step automation workflows with triggers, conditions, delays, and actions) do not migrate as automation code. The Journey configuration exports as JSON metadata covering triggers, steps, conditions, and delays. Freshsales Workflows (available on Growth tier and above) use a different trigger model (record-based and time-based rather than behavioral event-based). We deliver a written Journey inventory with each Journey's trigger type, step count, conditions, and recommended Freshsales Workflow equivalent. The customer's admin rebuilds the actual automation logic in Freshsales Workflows or routes it to a dedicated marketing automation tool if continued journey orchestration is required.

Zoho Marketing Plus Events (with registrations, session data, speaker info, and attendee records) split across two Freshsales objects. Event metadata (name, date, location, description, capacity) migrates as a Freshsales Task with custom fields capturing event-specific properties. Attendee records from Zoho migrate as Freshsales Contacts (if not already present) or as a custom Event_Attendee__c field on an existing Contact record. Session and speaker data that Zoho stores as sub-objects cannot map to a single Freshsales standard object; we flatten these into custom fields or related Tasks and flag them for manual structuring in Freshsales Admin Settings.

Zoho Webinar attendee records (registration status, attendance data, session links) migrate as Freshsales Contacts. Registration status becomes a custom picklist field (Registered, Attended, No-Show). Session-specific identifiers and Zoom/Webinar session links are stripped and replaced with placeholder text directing the customer to re-establish webinar integration post-migration. If webinar attendees are already present as Contacts in Zoho Marketing Plus, the attendee data appends as additional custom fields on the existing Contact record rather than creating duplicate contacts.

Zoho Marketing Plus custom Contact fields created via the Marketing Automation API migrate to Freshsales custom fields on the Contacts module. Supported field types mapping includes: text (Single Line Text), integer (Number), phone (Phone), date (Date), picklist (Picklist), email (Email), checkbox (Checkbox), multiselect (Multi-Select Picklist), datetime (Date/Time), decimal (Number). The customer must pre-create these custom fields in Freshsales Admin Settings with the exact same field names before migration begins so that the auto-mapping triggers. Field order and section placement do not migrate; these require manual layout configuration in Freshsales after migration.

Zoho Marketing Plus marketer accounts (admin, marketer, custom roles) migrate as User metadata. We extract user name, email, role designation, and brand assignment. The role names from Zoho are preserved as a custom field on the Freshsales User record because Freshsales User roles use a separate permission-set model. Brand scoping from Zoho multi-brand management maps to a custom Brand__c field on the Contact record rather than a native Freshsales concept. User provisioning in Freshsales is manual; we resolve users by email match and deliver a reconciliation list for the customer's admin to provision any missing Freshsales users before record import.