Phone Number Porting: A Migration Playbook for Nonprofits

Ask a nonprofit ED why they have not switched phone systems yet and you will often hear the same worry: "What if we lose our main number?" That number is on grant applications, IRS filings, decades of donor mail, the side of the outreach van, and Google. Losing it for even a day during business hours would be a real problem.

The good news: porting a phone number to a new provider is a well-defined regulated process, and when it is planned properly, callers do not notice anything happened. The bad news: nonprofits routinely mishandle small details that cause 24 to 72 hour outages. This playbook walks through what to do, in order, so your port lands cleanly.

What porting actually is (in 90 seconds)

A number port, formally called an LNP (Local Number Portability) request, is an authorized transfer of ownership for a phone number from one carrier to another. Your new provider submits paperwork to your old carrier, the old carrier validates it, and both sides agree on a specific date and time (the "FOC date," or Firm Order Commitment) when the number will flip. Local numbers typically port in 5 to 10 business days. Toll-free numbers often take 2 to 4 weeks because they route through a separate database (SMS/800).

The port itself, on the day it happens, usually takes 15 to 60 minutes of possible flakiness. Not days.

Before you sign anything: audit your numbers

Before you commit to a new provider, pull a complete inventory. Nonprofits with legacy PBX systems almost always find numbers they forgot they were paying for.

• Every DID (direct inward dial) number on your current bill, including fax lines and analog lines
• The current carrier of record for each number (not always who you pay: sometimes there is a reseller in between)
• The billing telephone number (BTN), which is the "anchor" number on the account
• Whether each number is truly needed, or whether it can be released
• Any numbers used for alarm panels, elevators, fire panels, or postage meters (these need special handling)

That last item is where multi-site nonprofits get burned. An old fax line still wired to the fire alarm panel cannot be casually ported without coordinating with the alarm vendor.

Gather the paperwork carriers actually check

Most failed ports fail for one boring reason: the information on the port request does not exactly match what is on file with the losing carrier. "Exactly" means comma-for-comma. If your carrier has "First Baptist Church Of Springfield" and you submit "First Baptist Church, Springfield," it can reject.

Collect these before you file:

1. A recent bill from your current carrier (within the last 30 days), showing the account number, BTN, and service address
2. The exact legal entity name as your carrier has it
3. The service address as your carrier has it (not your remit-to address)
4. A signed Letter of Authorization (LOA) naming the new provider
5. A full list of numbers to port, plus a clear note of which is the BTN

Sequence the cutover to protect your callers

Here is where a good implementation earns its keep. You do not want to wait for port day to discover your new phone tree has a broken extension.

1. Week 1 to 2: Stand up the new system with temporary numbers. Build the auto-attendant, add users, test call flows end to end.
2. Week 2: Forward one lower-priority line (say, a program line) to the new system and let staff use it live. Fix what breaks.
3. Week 3: Submit the port request for your main numbers. Confirm the FOC date in writing.
4. Port day, early morning: Verify DNS, SIP registrations, and 911 records are correct on the new platform. Have someone available to test-call from an outside line every 15 minutes during the window.
5. Port day, after cutover: Call from a mobile, from a landline, and from a Google Voice number. Test voicemail, transfers, and after-hours routing.
6. Week 4: Cancel the old service in writing. Do not cancel before the port completes: cancelling releases the number and the port will be rejected.

Common mistakes that cost nonprofits real money

• Cancelling the old carrier first. Numbers get released back to the pool, and reclaiming them is difficult or impossible.
• Porting on a Monday or Friday. Tuesday through Thursday mornings give your team time to troubleshoot without weekend gaps.
• Forgetting the 911 address. Ported numbers do not automatically carry E911 registration. Register each location on the new platform before port day.
• Not updating outbound caller ID. If staff had DIDs, make sure their outbound calls now show the correct ported number, not a placeholder.
• Missing SMS re-enablement. A/B texting on a ported number requires new 10DLC campaign registration. Start that paperwork the day you file the port.

The bottom line

A well-run number port is boring. That is the goal. The nonprofits that have painful migrations almost always skipped the CSR check, cancelled the old line too early, or tried to port on the same day they went live. Give yourself a four-week runway, keep the old service paid through cutover, and test relentlessly with real phone calls.

If you would like a second set of eyes on your number inventory before you commit to a provider, our team is happy to walk through it with you. A 20 minute audit call has saved plenty of nonprofits from a very long port day.