Moving a voice workflow between client subaccounts is a migration of business identities. A copied prompt can still mention the old business, call the old calendar, or notify an employee who no longer owns the customer relationship.
Start with a dependency inventory rather than the export button. List the phone route, authorized location, calendars, contact fields, tags, notification recipients, service rules, and every external action. Record which items contain destination-specific identifiers and which are genuinely reusable policy.
Treat location identity as a required input
Create the destination connection independently. HighLevel's OAuth guide describes selecting a location during installation. Verify that selected identity against the intended client before any test write.
Keep a migration map with source label, source identifier, destination identifier, and verification evidence. Matching display names are useful hints but insufficient proof. Two calendars named “Consultation” can belong to different businesses and have different appointment rules.
Work through a fictional clinic migration
Suppose a clinic moves from an agency-owned location to its own account. Its old workflow offers thirty-minute consultations and notifies the agency's coordinator. The destination uses forty-minute visits and an internal receptionist.
Copying the old settings would preserve the wrong duration and recipient. Instead, confirm the new duration with the clinic, create the target mapping, and test the entire conversation against the destination. Keep the old workflow available until the new one passes review, but prevent both from processing the same call.
| Migration case | Acceptance condition |
|---|---|
| Existing patient calls | Destination record is selected or reviewed |
| New consultation request | Correct duration and destination calendar |
| Calendar unavailable | Request stays pending without a promise |
| Staff notification | Only destination staff receive it |
| Rollback call | One active call handler receives the call |
Cut over the entry point last
Deploy destination configuration before changing live routing. Run approved test calls, inspect the resulting records, then switch the phone entry point during a staffed window. Record the exact cutover time so delayed events can be attributed to their original location.
Decide what happens to in-flight requests. Finishing them in the source is often easier to audit than moving half-completed work, provided the client retains access and agrees to that approach. Otherwise, migrate them through an explicit queue with owners and original identifiers.
A short overlap improves rollback options, but overlapping writers create duplicate outcomes. Keep only one workflow authorized to execute new customer actions at a time. Review location isolation using agency client isolation.
Questions about subaccount migration
Can prompts be reused unchanged?
Reusable conversation guidance can be copied, but verify business facts, pricing language, escalation routes, and action mappings individually.
Should historical contacts be migrated first?
Only when required for the new workflow and approved by the data owner. Contact migration has separate matching and retention decisions.
What proves the migration is finished?
A call routed through the live entry point produces the intended destination record, the correct staff notification, and a traceable action result. Keep a written rollback owner until the agreed review window ends.