What should be inventoried before a carrier provisioning migration affects number porting failure resolution history?
Inventory record classes, coverage, owners and deadlines, at metadata level only. The goal is a description a decision-maker can act on, not a copy of anything.
Ask the provisioning team five questions while the migration plan is still being written:
- Which record classes exist for failed ports? Original orders, supplements, rejection notices with reason codes, CSR requests, firm order commitments, activation confirmations, service desk tickets, and any port-out records if the company also loses numbers to other providers.
- How far back does each go? Years of orders in the platform, years of tickets in the service desk, and whether the shared mailbox holds rejections the platform never captured.
- Does the platform keep versions? If supplements overwrite earlier values, the original submission may already be gone for older orders, and the inventory should say so.
- Who owns each class? The provisioning director usually administers the order platform; customer care owns the service desk; IT runs the mail archive. Administration is not ownership.
- When does old-platform access really end? Use the date in the vendor contract or the decommission plan. If no date is set, record that; do not invent one.
If the company provides wireless service, add one more line. The FCC's 2023 SIM swap and port-out fraud rules require wireless providers to notify customers immediately of port-out requests and to investigate, remediate and document fraud reports. Those notification and fraud records are a distinct class with their own handling rules, and the inventory should list them separately from ordinary port failures.
Why failed-port history slips through a provisioning migration
A provisioning migration is planned around live service: active numbers, open orders, current customer accounts and the routing the network needs tomorrow. A port that failed, was corrected and completed three years ago is none of those things, so its full story is rarely in scope.
Three features of porting make the history easy to lose:
- The evidence is split between providers. The rejection, and the customer service record behind it, come from the old provider. What the company holds is its own copy, often in a shared mailbox rather than the order platform. The industry database is not a fallback: the NPAC is made up of seven regional systems that manage number portability for wireline, wireless and VoIP providers, and access is limited to authorized users and permitted uses.
- Ports move fast, so records are short and dated. The FCC says simple ports must be processed in one business day. Its 2010 order defines a simple port as one that involves a single-line account, no unbundled network elements, no complex switch translations and no reseller. Multi-line business ports fall outside that definition, so they run on longer intervals and leave more room for rejections and resubmissions.
- Corrections overwrite. A supplement that fixes a service address or account number may replace the original values. Unless the platform keeps versions, the wrong value that caused the rejection disappears from the order itself.
The inventory does not need to resolve any of this. It needs to say which copies exist, where, and for how long.
An illustrative inventory sheet
Illustrative only; the provider and figures are fictional. A 260-person business voice and connectivity provider is replacing its order and provisioning platform next year. Its provisioning director fills in the sheet from the migration plan and a few report counts, without opening a single order.
| Record class | System | Years held | Owner | Moves at cutover? | Readable until |
|---|---|---|---|---|---|
| Port orders | Order platform | 2018 to now | Provisioning director | Open orders only | Old platform contract end |
| Supplements and versions | Order platform | 2018 to now | Provisioning director | No | Old platform contract end |
| Rejection notices and reason codes | Order platform and shared mailbox | 2018 to now | Provisioning director, IT | No | Mailbox retention policy |
| Old-provider CSR copies | Shared mailbox | 2019 to now | IT, customer care | No | Mailbox retention policy |
| Service desk tickets | Service desk | 2017 to now | Customer care director | Not affected | Service desk kept |
Reading the sheet: the tickets are safe because the service desk is not changing. The order versions and rejection codes, which show what was wrong and how it was fixed, depend on the old platform contract and the mailbox retention policy, and both dates belong in the handoff.
Which date is the real deadline?
The date read access to the old order platform ends, as written in the vendor contract or the decommission plan. Go-live of the new platform is earlier and less important, because the old one may stay readable for some time after it. The second date to record is the shared mailbox retention period, because rejection notices that never reached the platform live only there. If neither date is fixed yet, write "not set" and move on.
Do not recommend keeping data the company has no authority or reason to keep. Port orders carry customer account details, and carriers have a duty under Section 222 of the Communications Act to protect customer proprietary network information. The inventory describes what exists; the company, with counsel, decides what is retained.
Does the provider qualify?
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English.
What stays unknown until SourceX reviews it: whether there is dataset demand for port failure records, what rights review concludes about copies received from other providers and about customer information, what must be removed, and whether any offer follows. Partners must sign the Channel Partner Agreement before submitting introductions; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. How a reward is calculated is on the rewards page. Neighboring record types are on the industries hub and the telecommunications page, and the telecommunications screening worksheet helps check fit before you raise it.
Go deeper on number porting failure resolution
- Number porting failure resolution exception examples: one failed port worked through step by step, with the record each decision left.
- Number porting failure resolution records across systems: a system map of the identifiers that join orders, rejections and tickets.
- Who can license number porting failure resolution records: a decision tree for which executive to introduce and what needs legal sign-off.
- Number porting failure resolution referral brief template: a fill-in, metadata-only brief for the company introduction.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the migration plan shows years of rejected ports with their supplements and tickets intact, register as a partner, check the provider against who qualifies, and read the program terms before you send the provisioning director the handoff brief.