Hello Trailblazers,
I'm planning to migrate our Pardot Classic org to Pardot Lightning and have a few questions before starting:
- User License: Our Pardot users currently have a Chatter/Chatter Free-type license. What license is actually required for Pardot Lightning access — will Chatter-licensed users work, or do they need to be upgraded first?
- Pre-Migration Checklist: What key things should we check or prepare before starting the switch — any pre-migration steps people often overlook?
- Existing Assets: Will our current email templates, forms, prospects, scheduled email for campaigns, and email domains carry over automatically, or do some need manual migration?
- Sales Cloud Impact: Does this migration affect our existing Sales Cloud (Lightning) production data in any way?
- Classic Access Post-Migration: After Lightning is set up, will pi.pardot.com (Classic) still be accessible, or is it fully deprecated at that point?
- Nonprofit Cloud Compatibility: Is Pardot Lightning compatible with Nonprofit Cloud orgs? Does the setup/migration process work the same way as it does for a standard Sales Cloud org?
Would appreciate hearing from anyone who's been through this migration — especially any gotchas not covered in the documentation.
Thanks so much in advance for your help !!
@* MC Account Engagement (fka Pardot) *2 个回答
- User License: Our Pardot users currently have a Chatter/Chatter Free-type license. What license is actually required for Pardot Lightning access — will Chatter-licensed users work, or do they need to be upgraded first? If you are referring to an "identity" license, these still work, but it still retains the limitations in that you can't access certain necessary features, like Salesforce campaigns. Ideally admins should have full salesforce licenses.
- Pre-Migration Checklist: What key things should we check or prepare before starting the switch — any pre-migration steps people often overlook? Normally what trips people up is getting the visibility of the app to the correct profiles. Follow the setup instructions carefully. Also the user/role mapping if you migrate Account Engagement user management to Salesforce is quirky. You still map profiles to roles in AE, but there's a whole different mapping in Salesforce. This article has some good tips.
- Existing Assets: Will our current email templates, forms, prospects, scheduled email for campaigns, and email domains carry over automatically, or do some need manual migration? There's really no change. It's just looking at the same data in a different interface. However, going on lightning also gives you access to the new CMS, landing page and email builders (which also have to be configured and access given to your users). These are in addition to, not replacing, the current Pardot resources.
- Sales Cloud Impact: Does this migration affect our existing Sales Cloud (Lightning) production data in any way? Only that there's a new Account Engagement App for the people that use it.
- Classic Access Post-Migration: After Lightning is set up, will pi.pardot.com (Classic) still be accessible, or is it fully deprecated at that point? Yes.
- Nonprofit Cloud Compatibility: Is Pardot Lightning compatible with Nonprofit Cloud orgs? Does the setup/migration process work the same way as it does for a standard Sales Cloud org? I would think so but I am not certain of that.
