The Hyperforce Assistant is not something you build, it is a Setup tool you run to prepare your org. Here is how to work through it.
- Open the Assistant in Setup
From Setup, type Hyperforce Assistant into the Quick Find box and select Hyperforce Assistant. Do this in a sandbox first if one is available, so you can rehearse before production.
- Work the Learn phase
Read the Learn phase with the team that owns the change. It explains what Hyperforce is and what shifts for your org, which sets context before anyone starts editing configuration or code.
- Run the Prepare checks
Move to the Prepare phase and let it run the org-contextual checks. Review the hard-coded reference and connectivity findings, each of which links to the matching help article with the fix.
- Remediate and rerun
Fix the flagged items, replacing instance URLs with My Domain URLs and updating firewall allow-lists, then rerun the checks. Repeat until the task list is clean before the scheduled migration date.
The guided overview of Hyperforce and what changes for your org. Start here so the people doing the work understand the why.
Scans for instance-specific URLs like na1.salesforce.com that should become My Domain URLs before the move.
Confirms the org can reach the target Hyperforce instance, catching firewall and allow-list gaps early.
Running the Assistant in a sandbox first to rehearse the preparation and predict a clean production cutover.
- The Assistant prepares your org but does not perform the migration. Salesforce schedules and runs the actual cutover.
- Hard-coded URL cleanup is usually the longest task. Start it weeks ahead, since references hide in integrations, Visualforce, WSDLs, email templates, and Chat.
- Firewall allow-list changes often sit with a network or security team, so identify the approver early to avoid a last-minute scramble.
- After July 1, 2026, per the Salesforce FAQ, it is no longer possible to delay upgrades to Hyperforce, so do not treat the date as flexible.