The Assistant runs in Setup. Plan a multi-week project from first scan to post-migration validation; the actual cutover takes hours, but the readiness work takes longer.
- Open the Hyperforce Migration Assistant
Setup, Quick Find, type Hyperforce. The Assistant page opens with current status, expected migration window, and a list of readiness tasks.
- Run the readiness scan
Click Run Scan. The Assistant evaluates the org against the current Hyperforce compatibility requirements and produces a list of remediation tasks.
- Work through readiness tasks
Address each task: update IP allow-lists, replace deprecated APIs, fix pod-URL references in code. The Assistant tracks completion as each task is resolved.
- Coordinate the migration window
Once readiness is green, work with the Salesforce account team to schedule the migration. The Assistant proposes a window; review with stakeholders, confirm or reschedule.
- Test in sandbox first
Migrate a sandbox ahead of production. Run integration regression tests, validate every external IP allow-list, confirm Apex callouts still work.
- Execute production migration
On the scheduled window, the org goes read-only briefly. The Assistant shows live status; users see a maintenance notice. Once complete, run post-cutover verification.
- IP allow-list updates require coordination with the customer''s network team. The Salesforce-side admin alone cannot fix firewall config; planning multi-team work is part of the migration.
- Custom code referencing pod URLs (na1.salesforce.com, na12.salesforce.com) silently breaks if the URL is hardcoded. Find every reference before migration day.
- Sandbox migrations precede production. Skipping sandbox validation increases the risk that production migration surfaces issues at the worst time.
- Customer Trust schedules migrations; admins cannot self-serve a date. Negotiation is required for tight-window orgs with regulated reporting deadlines.