Migrate from Salesforce Marketing Cloud Account Engagement to Freshsales

Prospects with lifecycle stages of subscriber, marketing qualified lead, or sales accepted lead map to Freshsales Lead. We apply a computed split rule during migration using the Pardot lifecycle_stage and hs_lead_status properties. The original Pardot lifecycle stage is preserved in a custom field pardot_lifecycle_stage__c on the Lead for audit and segmentation. Any active Pardot owner assignment is resolved to a Freshsales User by email before Lead creation.

Prospects with lifecycle stages of sales qualified lead, opportunity, customer, evangelist, or other map to Freshsales Contact. The original Pardot lifecycle stage is preserved in a custom field pardot_lifecycle_stage__c on the Contact. Contact is created after the related Account is established so the AccountId lookup is satisfied at insert time.

Pardot Custom Fields migrate as Freshsales custom fields on the Lead and Contact objects. Field type mapping applies: Pardot text, number, date, and picklist fields map to Freshsales equivalent field types. Required field constraints and picklist values are recreated in Freshsales before import. Pardot field labels are preserved as Freshsales field names with spaces retained for readability.

Pardot Prospects are associated to Accounts via the Salesforce CRM sync, but Account Engagement itself does not have a native Account object. We extract the linked Account name from the Pardot-Salesforce sync data and create Freshsales Account records. If no Salesforce Account is linked, we create the Account from the Prospects company field or use the email domain as a fallback dedupe key.

Pardot Campaigns track marketing initiative performance and associate to Prospects. We map Campaign records to Freshsales Deals, with the Campaign name becoming the Deal name and the Campaign budget or cost mapped to the Deal Amount field. Each migrated Deal is linked to the Account and Contact derived from the associated Prospects. Campaign-level Prospect activity history migrates as Deal-related tasks and notes.

Pardot Scoring Categories with custom weights and category names require manual rebuild in Freshsales. Freshsales Pro+ has native Fit Score and Engagement Score fields on Lead and Contact, but Pardot's custom Scoring Category logic cannot be imported as code. We export the category definitions and weight rules during scoping and deliver a written specification for rebuilding the scoring model in Freshsales scoring rules post-migration. Historical Prospect scores migrate as static custom field values for reference.

Pardot Custom Objects (available on Advanced+ tier) can reference Salesforce objects linked to Prospects. In Freshsales, we recreate the destination schema as Freshsales custom modules with lookup relationships to Contacts and Accounts. Custom object records migrate via the Freshsales REST API. Automation rules on custom objects (which Pardot marks as read-only) do not migrate.

Engagement Programs and Automation Rules are not migratable. They reference internal Pardot object IDs that do not exist in Freshsales. We export the full program structure during scoping, including trigger conditions, action sequences, wait steps, and completion actions, and deliver a written inventory for the customer's admin to rebuild as Freshsales workflows or a separate marketing automation tool. This is scoped as a separate rebuild project outside standard migration.

Pardot Forms capture Prospect data and are tied to Landing Pages and Custom Fields. Freshsales CRM has no native form builder equivalent. We export form definitions, field mappings, and handler logic as a written specification. The customer rebuilds forms in a separate form tool (Typeform, HubSpot Forms, or Freshworks Freshdesk forms) and maps field outputs to Freshsales custom fields. Form handler URLs cannot be migrated because they reference internal Pardot IDs.

Pardot Landing Pages are static web assets hosted within or pointing to Account Engagement, tied to internal form IDs. Freshsales CRM has no Landing Page object. We export page content, layouts, and associated form bindings as a written asset inventory. Landing pages are rebuilt in a separate CMS or form tool post-migration. The customer documents URL redirects for any indexed landing pages before decommissioning the Pardot instance.

Email Template HTML content migrates to Freshsales Email Templates. Merge field syntax requires rewriting: Pardot uses double-brace syntax such as %%first_name%% and Freshsales uses single-brace syntax such as {{contact.first_name}}. We rewrite standard merge fields during template export. Dynamic content blocks with conditional branching logic are flagged for marketer-level review and manual reconstruction rather than automated import.

Pardot Tags used for Prospect segmentation migrate as Freshsales Tags on Contact records. Tags export cleanly via the Pardot API as label-value pairs per Prospect. In Freshsales, Tags are a native segmentation feature available on Contact and Deal objects. Tag assignments migrate as tag membership records against the relevant Contact derived from the Prospect.

Pardot Static List memberships migrate as Contact records tagged with the corresponding list name. Dynamic Lists with rule-based criteria cannot migrate as active lists because the criteria engine differs between platforms. We export the dynamic list membership snapshot at migration time and deliver a written rule translation for rebuilding the equivalent Contact Group logic in Freshsales.

Pardot Business Units partition prospects, users, and branding within a single account. Freshsales has no Business Unit equivalent; it supports a single account with Teams for internal segmentation. For multi-Business Unit migrations, we migrate each Business Unit's Prospects as separate scoped imports and deliver a written configuration plan using Freshsales Teams, shared Products, and territory-based Assignment Rules to approximate the original Business Unit structure.

Pardot Users or Assigned Owners correspond to Freshsales Users responsible for Prospect records. We resolve Pardot user email addresses against the Freshsales User table. Any Pardot Owner without a matching Freshsales User goes to a reconciliation queue for admin provisioning before record import begins. Owner assignments on Prospects migrate as the OwnerId on the resulting Lead or Contact in Freshsales.