Migrate from Salesforce Marketing Cloud Account Engagement to Zoho CRM

Account Engagement Prospects have no direct Zoho equivalent because Zoho separates Leads and Contacts. We split Prospects into Zoho Leads (for records with no closed-won Opportunity and lifecycle stage indicating pre-qualified) and Zoho Contacts (for records linked to a Salesforce Account that we create as a Zoho Account, or for Prospects where the Pardot has_company_name flag is true). Email address is the sole identity key in Pardot — we use a three-pass match: exact email, normalised email (lowercased, punctuation stripped), then manual resolution queue. We preserve Pardot prospect_id in a custom text field pardot_prospect_id__c on both Lead and Contact for audit and source traceability.

Pardot Custom Fields map directly to Zoho CRM custom fields on the Lead and Contact modules. Field types map by Pardot type: text to single-line, textarea to multi-line, date to date, checkbox to checkbox, and multi-checkbox to Zoho multi-select picklist (note: Zoho multi-select is limited to 100 values per field; any Pardot multi-checkbox exceeding this requires splitting into two picklist fields or a tags-based approach). Custom field labels and API names migrate verbatim. We audit the total custom field count per module against Zoho's 300-field hard limit before migration.

Account Engagement does not have a native Account object — Prospects are associated to Accounts via the Salesforce CRM bidirectional sync. When migrating Prospects, we check the Pardot prospect_record_type and has_company_name fields to identify Prospects that were linked to a Salesforce Account. We create or match a Zoho Account for each unique company name, then link the corresponding Zoho Contact or Lead to that Account. If a Prospect has no company association, we create the Contact or Lead without an Account lookup.

Pardot Campaigns track marketing initiative performance and link to Salesforce Campaigns. We export Campaign metadata (name, type, status, budget cost, start and end dates) and Prospect-level activity data (opens, clicks, form submissions per Prospect). These activities map to Zoho Campaign Member records tied to the Campaign. Note that Zoho Campaigns do not support the same attribution modelling as Pardot's multi-touch attribution — we document the attribution model and recommend Zoho Analytics or a BI tool for post-migration reporting.

Pardot Scoring Categories define named buckets for behavioural and demographic scoring with per-category weight rules. Zoho CRM's scoring feature uses a single numeric score per module without named category support. We create a Zoho Scoring field (positive integer) and calculate the aggregate score by applying each Pardot Scoring Category's weight rules in a pre-migration script. We preserve the original Pardot Scoring Category definitions in a custom multi-select picklist scoring_categories__c so the customer's admin can rebuild named category logic in Zoho using Workflow conditions. We flag this as a configuration item requiring admin validation post-migration.

Pardot Tags are used for Prospect segmentation and attach to Prospects via the API. We export tag definitions and their assignments per Prospect. Tags migrate to Zoho as a multi-select picklist field (tag_name__c) on the Lead or Contact module. If the customer's Zoho edition supports the native Tags feature, we map to Zoho's built-in tagging instead of a custom field. The customer selects the tagging strategy during scoping.

Pardot Static Lists and Dynamic Lists segment Prospects. We export list memberships as Lead and Contact records per list. Static lists map cleanly as Zoho custom modules or tags. Dynamic lists with rule-based criteria are not migratable as active filters because Zoho's filter logic differs from Pardot's list rule syntax. We deliver the list definitions as a written inventory of the filter criteria and member counts for the admin to rebuild as Zoho saved filters or Workflow-based segmentation.

Pardot Users (Assigned Users / Owners) correspond to Salesforce Users responsible for Prospect records. We extract the Pardot assigned_to, owner_id, and user_email fields from each Prospect. We match by email against the Zoho CRM User table. Any Pardot Owner without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision the User before record import resumes. Zoho's User provisioning is scoped to the admin during discovery.

Pardot Email Templates contain HTML content, dynamic content blocks, and merge fields using %%field_name%% syntax. We export template HTML and rewrite merge field syntax to Zoho CRM's {{Lead.FieldName}} and {{Contact.FieldName}} format as part of the export step. Dynamic content blocks and conditional logic (IF/ELSE branches in Pardot) require manual review and reconstruction at the destination because Zoho Email Templates do not support the same conditional branching model. We flag templates with complex dynamic content for marketer-level rebuild.

Pardot Prospect engagement history (email opens, link clicks, form submissions, page views) is stored as visitor activity records linked to Prospects. We export these as Zoho Notes or custom activity log records linked to the migrated Lead or Contact. Note that Zoho does not have a native visitor-activity tracking equivalent — the activity log is a historical record, not a live tracking feed. Engagement timestamps migrate as-is to preserve the original activity chronology.

If the Pardot-Salesforce sync included Account-level or Opportunity-level custom fields, we map these to Zoho CRM custom fields on the Account and Potential modules. We apply the same type-mapped field creation approach and audit against Zoho's 300-field limit per module. Opportunity-level fields map to Zoho Potential (Deal) module custom fields.