Migrate from Salesforce Marketing Cloud Account Engagement to monday CRM

Account Engagement Prospects map directly to Monday.com CRM Contacts. Email address is the dedupe key on both systems. We use a three-pass matching strategy: exact email match, normalised email match (stripped of case and whitespace), then flagged for manual resolution. Prospect-level fields including first name, last name, phone, company name, title, city, state, and country migrate as native Contact fields. We flag any Prospects with duplicate emails for customer review before import to prevent unintended merges.

Pardot Custom Fields migrate to Monday.com Item custom columns on the Contacts Board. We map field types: text fields become Text columns, date fields become Date columns, picklist fields become Dropdown columns, and multi-select fields become Multi-select columns. Boolean fields map to Checkbox columns. The Pardot field label becomes the Monday.com column name. Custom fields are scoped to the Contacts Board; any cross-object custom fields require Monday.com integration Board design or separate text storage.

Pardot Tags migrate to Monday.com Tags on the Contacts Board. Tags are a flat namespace in both platforms, so the migration is direct. Multi-value tags per Prospect export as individual tag assignments and import as separate tag rows per Contact. We flag tags used for scoring or grading logic because Monday.com has no automated scoring mechanism; these tags serve as static segmentation markers post-migration.

Account Engagement does not have a native Account object; Prospects are linked to Salesforce Accounts via the Pardot-Salesforce Connector. If the customer exports Company data from Account Engagement (the Prospect company_name field or a linked Salesforce Account export), we map it to Monday.com Organisations. Monday.com Organisations serve as the parent entity for Contacts and contain Company-level data. We resolve the Account-to-Organisation mapping by Prospect company name where no Salesforce Account export is available.

Account Engagement Campaigns track marketing initiative performance and link to Salesforce Campaigns. Monday.com has no native Campaign object. We offer two migration strategies during scoping: campaigns map to Tags on the Contacts Board (simple, static), or campaigns map to a separate Monday.com Board with campaign metadata as columns and linked Contacts as Items (more structure, requires Board redesign). The customer selects the strategy. Campaign performance data (sends, opens, clicks) does not transfer because Monday.com does not track email engagement.

Pardot Users (Assigned Users) who own Prospect records map to Monday.com Team Members. We match by email address. Any Pardot user without a matching Monday.com account goes to a reconciliation queue for the customer's admin to provision. Inactive Pardot users can be migrated as inactive Monday.com members if historical assignment ownership must be preserved.

Account Engagement Engagement Programs and Automation Rules reference internal Pardot object IDs that have no equivalent in Monday.com. Monday.com has no automation builder, no trigger-based sequence engine, and no multi-step nurture capability. We do not migrate these as active workflows. We document the full program structure during scoping: trigger conditions, step sequences, wait durations, and action types. The customer receives a written Automation Rebuild Guide that describes each Pardot program and its recommended Monday.com manual equivalent, typically a set of Tasks and Follow-ups that the sales team creates manually or via Monday.com Automations at the basic level.

Account Engagement Email Templates contain HTML with Pardot merge field syntax (%%first_name%%) and dynamic content blocks. Monday.com has no native email template system, no email sending capability, and no merge field engine. We export the template HTML and merge field list as a reference document. The customer uses this to rebuild templates in their chosen email platform (Mailchimp, Klaviyo, or a dedicated email tool). Dynamic content blocks and conditional logic require complete manual reconstruction.

Account Engagement Scoring Categories define named weight buckets for grading Prospects (e.g., behavioural score versus demographic score) and combine into a total score. Monday.com has no scoring model and no equivalent to grade or score fields. We export the scoring category definitions and weight rules as a reference document. The customer rebuilds scoring using Monday.com numeric custom columns updated manually or via an external scoring tool integrated through Zapier or the Monday.com API.

Account Engagement Forms capture Prospect data and are tied to Landing Pages and Custom Fields. Monday.com does not have a native form builder for lead capture. We export form definitions, field mappings, and handler URLs as reference documentation. The customer rebuilds forms in a dedicated form tool (JotForm, Typeform, HubSpot Forms, or their website CMS) and maps submissions to Monday.com Contacts via Zapier or native integration.

Account Engagement Landing Pages are static web assets hosted within or referencing internal form IDs. Monday.com has no landing page builder. We flag landing page URLs for the customer's web team to update or redirect. The internal form IDs on landing pages have no equivalent in Monday.com.

Pardot Static Lists and Dynamic Lists segment Prospects for targeted campaigns. Monday.com has no native list segmentation equivalent. Static list memberships migrate as Tag assignments on the relevant Contacts. Dynamic lists with rule-based criteria do not migrate as active segments; we document the list criteria so the customer can recreate equivalent Views in Monday.com (filtered Contact views by tag, date range, or custom column value).