Quick answer: EU copper retirement is not one deadline — it is a stack of national regulator calendars that European incumbents withdraw exchange-by-exchange on their own second-generation schedules. Deutsche Telekom, Orange, Telefónica, TIM, KPN, Telia, and the other member-state operators each publish their own per-country windows, and every tranche moves its earliest cut-off forward when downstream take-up stalls. The tenant-owned answer is the PSTN switch-off explainer applied per member state: inventory every copper-fed line country by country, get each carrier's exchange-level notice in writing, decide between a BYO SIP trunk or a port for that country's lines, run the port as early as the paperwork is clean, and cut over in tranches with a rollback window. This runbook walks that per-country checklist for European buyers and links the shipped Orbit SIP/BYO and porting controls the checklist uses.
If you are new to copper retirement itself, read the sibling PSTN switch-off copper-retirement explainer first — it covers what the switch-off is and what a carrier relationship demands after the bearer dies. This post assumes that explainer and goes narrow on the European phasing problem: twenty-seven member states, no EU-wide cut-off date, and national regulator calendars that drift on their own schedules.
Why European copper retirement is a phasing problem, not a date
The UK's Openreach programme is centrally coordinated: Ofcom blesses the nationwide calendar, exchanges are announced in tranches, and the entire country tracks one programme on one register. None of that holds inside the European Union. Each member state runs its own national regulator — Germany under the Bundesnetzagentur, France under ARCEP, Spain under the CNMC, Italy under AGCOM, the Netherlands under the ACM, the Nordics under their own national telecom authorities — and each incumbent publishes its own second-generation exchange-withdrawal schedule on top of that. In practice that means:
- One tenant, many calendars. A single European operation with lines in Germany, France, Spain, Italy, the Netherlands, Sweden, Denmark, and Poland carries eight parallel retirement calendars. The earliest one is the operative constraint for sequencing the whole move.
- The calendars move. Every incumbent revises its tranche announcements when downstream take-up lags. Deutsche Telekom's All-IP programme, Orange's fibre-only access, Telefónica's copper-close programme, TIM's folio rollover, KPN's KPN Glas release, and Telia's All-IP transition have each been recast since their first announcements. Treat a published date as a receding upper bound, never as a deadline you plan around.
- Different retirement shapes. Some markets flip the whole copper access product on a published date; others retire exchange-by-exchange on rolling 24-month notices; a few (Telia is the canonical example) retire the copper bearer even while the last-mile fibre migration is still taken in tranches. The retirement shape matters more than the headline date — it decides whether your written notice is one date, or a sequence of dates per line group.
The constant across all of it is that the tenant owns the migration. No European regulator obliges the incumbent to migrate you to IP under the same commercial terms, and no platform (Orbit included) can make the notice come sooner. Budget against the earliest plausible window per country, not the latest published one.
The per-country tenant-owned checklist
This is the same checklist the PSTN switch-off explainer gives generically, re-cut for the European per-country shape. Run it country by country; within a country, run it exchange area by exchange area.
- Inventory copper-fed lines per member state. PBX trunks, desk phones, fax, alarms, lifts, door entry, EPOS, and payment terminals, tagged by country and incumbent. A European estate almost never surfaces cleanly inside one carrier portal — the inventory is a spreadsheet you build yourself, and the incumbent tags on the line are what the checklist consumes next.
- Get the exchange-level notice in writing, per carrier. Published national tranches are directional; the incumbent's written notice for your exchange area is the budget line your CFO is planning against. For multi-country estates, this means eight written letters, one per carrier, every time the tranche moves.
- Decide BYO-carrier vs port per country. Keep the incumbent relationship and point a SIP trunk (BYO carrier) where the national regulatory position makes portability painful, where the rate structure is locked in, or where the incumbent bundle is worth preserving. Port the numbers onto the platform carrier where you want one termination relation. Both postures are documented in the SIP trunking and BYO carrier guide on the trunk side and the phone number porting guide on the port side.
- File ports early — the LNP clock is the long pole. A European port takes weeks to months depending on the member state, and the losing carrier's review clock only starts once the paperwork is clean. Filing the letter of agency after the tranche lands is discovering the critical path at the worst time of the year.
- Stand up trunks while the copper still works. SIP trunks authenticate and the failover chain routes to the secondary before the migration is a routing change, not a day-of downtime exercise. The BYO carrier guide documents per-trunk digest auth, IP allowlisting, per-attempt auth logging, and the failover walk your trunks should be running before the first cut-over.
- Convert or retire the non-telephony line groups. Alarm circuits, lifts, fax, payment terminals, door entry — the lines nobody filed as telephony, per the generic explainer. Each needs an IP converter, a replacement service, or a decommissioning decision before the copper goes. These are the lines that fail silently post-cutover.
- Cut over in tranches with a rollback window per tranche. Move one line group end to end per migration window, verify inbound routing plus outbound egress over the platform's own termination, then roll the remainder country by country. Published windows recede; rollback windows keep you inside the margin you actually control.
The tenant-owned posture in one paragraph
Copper retirement removes the bearer, not the numbers — exactly as the generic PSTN switch-off explainer frames it. The tenant owns the sequence: inventory per country, notices in writing per carrier, BYO or port per country, port paperwork filed early, trunks stood up while the copper still works, non-telephony converted or retired, cut-over rolled in tranches. Orbit supplies the shipped controls the checklist leans on — the SIP trunk ingestion at BYO-carrier posture, the bulk portability screening, in-platform LOA signing, the per-stage port timeline, and the webhooks at each state change — and deliberately does not run the migration for you. Carrier selection, cut-over sequencing, regulatory notices, and the migration calendar stay in your hands; the platform is the routing, porting, and visibility surface the checklist calls.
Outbound termination stays the same one way regardless: on Orbit, outbound PSTN egress runs over Devotel's wholesale softswitch in every posture, so the BYO-or-port answer is an inbound-delivery and commercial-preservation question, never an egress-routing question.
Where the checklist next links
The seven-step checklist above resolves to three already-published posts; each step links the surface it uses end to end:
- The PSTN switch-off copper-retirement explainer defines the bearer-retirement and the two tenant-owned decisions.
- The SIP trunking and BYO carrier guide covers keep-the-carrier posture, trunk authentication, and the failover chain the checklist stands up in step 5.
- The phone number porting guide covers the port posture end to end — the bulk screening, the combined readiness pre-validation, LOA upload and signing, the per-stage timeline, and the webhooks.
- The Devotel Orbit pricing surface discloses the per-country SIP and porting economics that the BYO-vs-port decision in step 3 prices against.
Frequently asked questions
Is there one EU-wide PSTN switch-off date?
No − the European Union has no single copper-retirement date. Each member state runs its own national regulator calendar, and each incumbent publishes its own second-generation exchange-withdrawal schedule. Twenty-seven member states means twenty-seven timelines, with national regulators (BNetzA, ARCEP, CNMC, AGCOM, ACM, and the Nordic equivalents) blessing them separately.
Which European carriers are retiring copper, and how?
Deutsche Telekom (All-IP), Orange (fibre-only access), Telefónica (copper-close programme), TIM (copper rollover), KPN (KPN Glas), and Telia (All-IP) have each published their own national windows. The retirement shape differs by carrier — whole-country date, exchange-by-exchange tranches, or a rolling 24-month notice — and the commissioned steps above key off the shape, not the headline date.
Do we port the numbers, or keep the carrier and SIP them?
Either — and the answer is a per-country decision, not a Europe-wide one. Keep the incumbent carrier and point a SIP trunk (BYO carrier) where portability is painful or the rate structure is worth preserving; port the numbers onto the platform's carrier where you want one termination relation. Mixed estates across a European operation are normal and deliberate.
How long does a European number port take?
Weeks to months, depending on the member state's regulator and the losing carrier's LNP process. The reviewing clock only starts once the paperwork is clean, so the checklist files the letter of agency before the tranche announcement lands, not after.
Does Orbit operate and run the migration for us?
No — deliberately. Orbit supplies the shipped SIP trunk ingestion, the bulk portability screening, combined readiness pre-validation, in-platform LOA signing, per-stage timelines, and per-state webhooks. The regulatory notices, the carrier-selection decision, the cut-over sequencing, and the migration calendar stay tenant-owned.
The takeaway
European copper retirement is a phasing problem, not a deadline problem. Every member state runs its own national calendar, every incumbent moves its own schedule when take-up lags, and the earliest plausible window per country is the constraint your migration budget runs against. A European tenant that inventories copper-fed lines per country, gets exchange-level notices in writing per carrier, decides BYO-carrier versus port per country, files the LOA early, stands up SIP trunks while the copper still works, and rolls cut-overs in tranches will absorb the whole wave as a routing exercise. A tenant that waits for the managed conversion will absorb it as an outage with procurement attached. The Devotel Orbit surface prices the SIP and porting decisions the checklist runs against; the calendar stays tenant-owned.
Published 22 September 2026.