Porting Numbers to Google Fi: Wireline vs Wireless Challenges

---

Understanding Wireline vs Wireless Number Classification

Wireline numbers originate from traditional landline providers such as cable or VOIP services like Comcast, AT&T wireline, or Google Voice. These numbers are routed via fixed copper or fiber infrastructure. Wireless numbers, on the other hand, are mobile and issued by cellular carriers like Verizon Wireless and T-Mobile, using radio spectrum. The distinction is stored in the Number Portability Administration Center (NPAC) database, mandated by FCC LNP rules since 1996.

Classification	Examples	Typical Port Time to Google Fi	FCC-Regulated Traits
Wireline	Landlines, Google Voice, VOIP (e.g., Spectrum Voice)	Up to 2 business days	Fixed location; requires account number, PIN, billing ZIP; higher rejection risk if misflagged as wireless
Wireless	Mobile (e.g., old Verizon/AT&T mobile)	Within 3 hours	Portable across carriers; needs account PIN; faster due to wireless LNP standards

Google Fi's port process prompts users to select the type during signup via the app, pulling carrier details for validation. However, no Google Fi page explicitly defines "wireline vs. wireless"; users must infer from port timelines and FCC documents. The FCC consumer guide confirms that carriers query NPAC for type before approving ports¹.

Why Google Fi Requires Accurate Classification

As an MVNO, Google Fi must comply with FCC LNP regulations which segregate porting paths: wireless-to-wireless uses streamlined Wireless Number Portability (WNP), while wireline-to-wireless involves inter-modal coordination. This is necessary for Google Fi to:

• Route requests to the correct donor carrier system.
• Avoid Number Pooling blocks: Wireless ports can't pull from wireline pools.
• Generate accurate Facilities Request Number (FRN) or port orders, as wireline ports often need physical address verification.

From Google Fi support: "Mobile numbers and numbers from Google Voice usually transfer within the first 3 hours. Landlines usually transfer within 2 business days." This timeline split implies backend classification—Google Voice (VOIP/wireline-equivalent) follows landline rules. Instructions warn: "Be ready to give account info from your current carrier," which varies by type.

How Misclassification Causes Port Failures

Mislabeling a number's classification can lead to port rejections. Carriers rely on the NPAC database to verify the type of number being ported. If a number is incorrectly classified, the port request may be rejected, causing delays and requiring resubmission with corrected information. Users should verify their number's classification through the Google Fi app or by contacting support.

Disclaimer

This article provides general information about porting numbers to Google Fi and is not a substitute for professional advice. For specific guidance, consult the official Google Fi support page or the FCC consumer guide.

---

For more insights on managing your Google Fi account, check out our guide on Google Fi features and learn about troubleshooting common porting issues.

Footnotes

1. Carriers query NPAC for number type before approving ports, as per FCC guidelines. ↩