Delivery and Migration17% of the exam
Premigration report, email cleanup and scheduling
The premigration work that decides whether a migration goes smoothly: org setup with SSO and billing, email cleanup against the identity provider, reading the premigration report, role conflicts, identity-provider and audit-log steps, verified workspaces, scheduling around downtime and the end-user announcement.
Plan and complete pre-migration activities (scheduling, user cleanup, comms, etc.).
~7 min read · 12 practice questions ·
What the exam expects
- Set up the destination org first: SSO, linked billing, no preprovisioned members.
- Run email cleanup, the most important premigration task, using the right premigration report sections.
- Predict how role conflicts and duplicate usernames resolve, and which settings the org overwrites.
- Add the identity-provider, audit-log and Skip SSO token steps a scenario needs, and order migrations (verified workspace first).
- Schedule around downtime and write the end-user announcement.
Key terms:
- Premigration report: a Slack-produced analysis of likely conflicts between migrating workspaces and the org.
- Lift and shift: one workspace migrating into an empty Enterprise organization (Enterprise Grid or Enterprise+ plan), with no data conflicts.
- True positive / false positive: a flagged username that is the same person with two emails, or two different people sharing a username.
- Skip SSO token migration: a migration setting that stops SSO token information carrying over.
Key facts
Most important task
- Detail
- Email cleanup to match the IdP
Paid workspace scheduling
- Detail
- Blocked until its billing is linked to the org
Premigration report delay
- Detail
- 24 hours; not exhaustive
Always overwritten by org
- Detail
- All sign-in settings, file retention, DM retention
Both accounts enabled, roles differ
- Detail
- Higher role kept, lower-role access removed
Skip SSO token migration
- Detail
- Off by default; on when switching IdP or in M&A
SAML workspace
- Detail
- Turn off IdP account provisioning before disabling the connector
Audit logs
- Detail
- Export before migration
Weekend or weeknight slot
- Detail
- Highly encouraged for 12+ hours of hard downtime
Migrations into one org
- Detail
- At least 24 hours apart
Sources for this section (5)
- Complete Premigration Stepstrailhead.salesforce.com (opens in a new tab)
- Prepare for Migrationtrailhead.salesforce.com (opens in a new tab)
- Premigration Clean-Uptrailhead.salesforce.com (opens in a new tab)
- Migrate workspacesslack.com (opens in a new tab)
- Migration Portaltrailhead.salesforce.com (opens in a new tab)
- Why is email cleanup the most important premigration task?
- Which two report sections drive email cleanup?
- When should Skip SSO token migration be checked?
- Why should a client not preprovision members into the org before migrating?
- What must happen before a separately billed paid workspace can be scheduled?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Slack Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 38 lessons of the Slack Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (12 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams