How to Move Phone Numbers in Sparkforge: Migration Guide

By Sparkforge Support Team ·Last reviewed May 3, 2026

Sparkforge handles phone number migrations end-to-end across five cases. Gather the right IDs (Twilio Account SID for US, Regulatory Bundle and Address SID for international) and open a Support ticket.

This guide covers moving an existing phone number in or out of Sparkforge so calls and SMS keep working. Open a Sparkforge Support ticket with the right IDs and a preferred cutover window. Sparkforge Support coordinates the migration end-to-end. You no longer need to open a Twilio support ticket.

Before you start

Gather these identifiers based on the numbers you're moving:

US numbers: Twilio Account SID (gaining for outbound moves, losing for inbound), destination sub-account ID, and the phone number(s).
International numbers: Regulatory Bundle SID, Address SID, and the phone number(s) including country.

Five migration cases

Case 1: Sparkforge to Twilio

Use this when moving a number from Sparkforge into your own Twilio account. For US numbers, include the gaining Twilio Account SID, destination subaccount (if used), and the numbers. For international, provide the Regulatory Bundle SID and Address SID instead of the Account SID.

Case 2: Twilio to Sparkforge

Use this when moving a number from your Twilio into Sparkforge. For US numbers, include the losing Twilio Account SID, destination Sparkforge sub-account ID, and the numbers. For international, include Regulatory Bundle SID and Address SID.

Case 3: Sparkforge to Sparkforge (different agencies)

Use this when moving a number between two different Sparkforge agencies. Provide the relevant Twilio Account SID for US (or Regulatory Bundle SID and Address SID for international), the destination agency and sub-account ID, and the numbers.

Cases 1, 2, and 3 follow the same process: provide the appropriate Twilio Account SID (gaining or losing), destination sub-account ID, and numbers. International moves use Regulatory Bundle SID and Address SID instead.

Case 4: Sparkforge to Sparkforge (same agency)

Use this when transferring a number between two sub-accounts inside one Sparkforge agency. The built-in Move Numbers tool handles it: Settings > Phone Integration > Move Numbers. Pick source numbers, choose the destination sub-account, and complete the transfer. It supports Sparkforge Phone to Sparkforge Phone and transfers across Twilio-connected sub-accounts under the same Twilio master. If the tool fails, contact Support with source and destination location IDs.

Case 5: Port a non-Twilio number into Sparkforge

Use this when your number sits with a non-Twilio carrier and you want it managed in Sparkforge. Gather the numbers and any carrier paperwork, then open a Support ticket with your desired cutover window.

Two-step process at a glance

Collect required IDs and numbers.
Open a Sparkforge Support ticket with those details and a preferred cutover window. Sparkforge coordinates the migration and confirms when traffic is live.

After completion, run quick inbound and outbound call and SMS tests on every number.

Frequently Asked Questions

Do contacts, conversations, and analytics move with the number?

No. Migration changes number ownership and routing only. Export any data you need to keep before cutover.

Do call recordings and voicemails migrate?

No. Future recordings and voicemails follow the number after cutover, but historical recordings do not transfer. Download anything you need to keep first.

Do A2P and Toll-Free approvals transfer automatically?

Not always. After the move, confirm your numbers are attached to the correct A2P brand/campaign or Toll-Free verification.

Can I move multiple numbers at once?

Yes. Include the full list (CSV or inline) in your Support ticket. Validate every number after cutover.

What if I need to roll back?

Reply to the Support ticket immediately during the cutover window. Rollback options depend on the carrier and timing.