Migrate Legacy Campaigns to Engagement Builder
- Audit your campaigns to identify eligible audiences and campaigns.
- Eligible audiences use advanced custom report types and are web-service enabled.
- Eligible campaigns have an end date that is:
- Current
- Blank
- Future
- Ensure your integration system user (ISU) has access to the audiences slated for conversion.
- Suspend the schedule for all active campaigns slated for migration to prevent overlapping processes.
- Create a new template using Notification Designer, which you attach to every notification selected during the migration process. Migrated templates are read-only. See Create and Activate Notifications.
- Do not start a migration immediately before or during scheduled system maintenance.
- Security:Manage: Campaign Migrationdomain in the System and Learning Core functional areas.
You can identify and migrate eligible audiences and campaigns from the
Campaigns
dashboard to the Engagement Builder
report. Campaigns adopt the Engagement Builder scheduling cadence of 4 runs a day.To prevent disruption, migrated campaigns do not trigger duplicate assignments or notifications, and they won't reassign waived assignments. Once migrated, you cannot revert audiences, campaigns, and message templates to Campaigns.
For a use case related to this topic, see Use Case: Migrate Legacy Campaigns in the Use Case Library.
- Access theMigrate Legacy Campaigns to Engagement Buildertask.
- Enter your filter criteria and clickApply Filters.
- Select the eligible campaigns and clickOK.
- From theIntegration System User (ISU)prompt, select your ISU.
- From theNotification Designer Templateprompt, select your template.
- ClickConfirmandOK.
Workday sorts the selected campaigns into 3 categories:
- Campaigns Ineligible
- Campaigns Migrated Successfully
- Campaigns Migration Failed
You can view successfully migrated campaigns on the
Engagement Builder
report. Workday replaces the legacy schedules with the Engagement Builder’s automatic schedule, which runs 4 times daily. Exact schedules for legacy reminders do not migrate. The Engagement Builder run log only displays activity that occurs after the migration.