MARKETING-CLOUD-ACCOUNT-ENGAGEMENT-CONSULTANT practice question 27 of 35

LenoxSoft has two Marketing Cloud Account Engagement accounts: Account A and Account B. Both accounts are syncing with the same Salesforce org. Their marketing teams have consolidated and have decided to merge Account B into Account A. What action should they take to successfully complete the migration?

Full set: 264 questions

Domain Email Marketing

Answer options
A: Include prospect activity history from Account B in their prospect import if they want to retain it.
B: Get a brand new Marketing Cloud Account Engagement org and migrate both Account A and Account B into it.
C: Export existing custom field mappings to import desired fields into Account A.
D: Manually rebuild any automations built in Account B in Account A. Correct answer
Correct Answer:
D. Manually rebuild any automations built in Account B in Account A.
Explanation

When merging one Marketing Cloud Account Engagement (formerly Pardot) business unit into another, marketing automation assets cannot be transferred automatically. This includes Engagement Studio programs, automation rules, completion actions, and dynamic lists. These components contain the core business logic for lead nurturing, scoring, and assignment. Therefore, a critical and mandatory step in the migration process is to manually audit, document, and rebuild these automations in the destination account (Account A) to ensure marketing processes are preserved and function correctly post-merger.

Why Incorrect

A. Include prospect activity history from Account B in their prospect import if they want to retain it. This is technically not possible. Prospect activity history (email opens, clicks, page views, etc.) cannot be exported and imported between Account Engagement accounts.
B. Get a brand new Marketing Cloud Account Engagement org and migrate both Account A and Account B into it. This is a more complex and costly alternative strategy, not a required action for the specified goal of merging Account B into Account A.
C. Export existing custom field mappings to import desired fields into Account A. Field mappings cannot be exported and imported. Custom fields and their corresponding mappings to Salesforce must be manually recreated in the destination account.

References

1. Salesforce Help: Considerations for Migrating from One Pardot Account to Another.

This document explicitly lists what can and cannot be migrated. Under the "What Can't Be Migrated" section, it includes: "Automation Rules," "Engagement Programs," "Dynamic Lists," and "Completion Actions." It also states, "Prospect activity history can't be migrated." This directly supports why option D is correct and options A and C are incorrect as described.

2. Salesforce Architects: Marketing Cloud Account Engagement (Pardot) for Architects.

In the section discussing multi-business unit strategy and consolidation, the guide implicitly supports the manual nature of asset migration. It emphasizes planning for data, assets, and automation recreation, stating, "There is no 'magic button' to move assets or settings between business units... Plan for a manual migration of any required assets." This reinforces that automations must be manually rebuilt (Option D).

Scroll to Top