Migrate from Freshmarketer to Zoho CRM

Freshmarketer Contacts map directly to Zoho CRM Contacts. Email address is the deduplication key. We preserve the original Freshmarketer lifecycle_stage in a custom field fm_lifecycle_stage__c for reporting continuity. Owner assignment resolves by email match against the Zoho User directory; missing users go to a reconciliation queue for admin provisioning before contact import proceeds.

Freshmarketer Companies map to Zoho CRM Accounts. The org_contact_id relationship in Freshmarketer becomes the Account Name lookup on the Contact record in Zoho. We pre-create Accounts before Contacts so that the Account-Contact lookup is satisfied at insert time. Domain from Freshmarketer becomes the Website field on Account.

Freshmarketer Deals map to Zoho CRM Deals with pipeline stage names and probabilities preserved. We configure Zoho pipeline stages before migration to match Freshmarketer stage labels and set probability percentages to match. Deal Owner resolves via email-to-User lookup. Custom deal fields require explicit field-type mapping (dropdown vs. text, date format alignment) during the field-mapping phase.

Freshmarketer email conversations, calls, meetings, and tasks migrate into Zoho CRM Activities. We use the Activity module's composite structure where Email type activities preserve body and timestamp, calls preserve duration and disposition, meetings preserve start time and attendees, and tasks preserve status and due date. Activities attach to the resolved Contact or Account record via the Parent ID.

Freshmarketer's Marketing Contacts billing concept (contacts targeted in email, SMS, or WhatsApp campaigns) has no native Zoho equivalent. We flag which contacts carried the marketing-contact status at migration time by setting a custom checkbox field fm_marketing_contact__c on each Zoho Contact. This lets the customer assess post-migration billing exposure and segment marketing-involved contacts for re-enrollment in Zoho Campaigns or third-party email tools.

Freshmarketer Segments define audience filters for campaign targeting. Zoho CRM does not have a native Segment equivalent. We map segment membership to Zoho CRM Static Lists (contacts added by explicit membership) or Dynamic Views (contacts filtered by criteria matching the segment logic). The customer chooses the approach during scoping; static lists are used when segment criteria cannot be replicated in Zoho's filter syntax.

Freshmarketer Journeys cannot be exported as executable logic via API. We capture the Journey configuration (trigger, conditions, steps, delays, enrolled contact count at cutover) in a written rebuild guide mapped to Zoho Blueprint and workflow rules. Active Journey enrollment state is captured per contact so the customer can replay mid-funnel contacts in the new platform. Rebuilding Journeys in Zoho Blueprint is a manual admin step documented in the migration handoff package.

Freshmarketer Users map to Zoho CRM Users by email address. We extract all distinct owners referenced on Contacts, Companies, Deals, and Activities and match against the Zoho User table. Users without a matching Zoho account go to a reconciliation queue for admin provisioning before record import continues.

Freshmarketer Tags migrate as flat string values attached to the corresponding Zoho Contact, Account, or Deal. Zoho CRM Tags are a native tagging feature available from Standard tier. Tags do not have hierarchy in either platform.

Freshmarketer Products map to Zoho CRM Products with product code, unit price, and description preserved. We create Products in Zoho before Deals to satisfy the product lookup on Deal Line Items.

Freshmarketer file attachments on contacts, companies, and deals export to a file store and load into Zoho CRM Attachments linked to the parent record. We preserve the attachment association by resolving the parent record ID at migration time. Large attachment volumes (over 1 GB total) may require batched loading via Zoho's API rather than the bulk import wizard.

Custom fields on Freshmarketer Contacts, Accounts, and Deals map to Zoho custom fields of equivalent type. Field-type differences (dropdown vs. picklist, multi-select, date format) are resolved during the field-mapping phase before migration. We pre-create custom fields in Zoho via the Zoho Settings API before any data import to avoid import errors from missing target fields.