Cloud PBX Migration Checklist for Luxembourg Businesses

Cloud PBX Migration Checklist for Luxembourg Businesses

Migrating from a legacy phone system to a Cloud PBX touches more parts of a business than most leaders expect. Done well, customers and staff barely notice. Done badly, calls are lost for a week and trust takes months to rebuild. Nearly every problem comes from a small set of steps that get skipped or rushed.
This checklist walks through every phase of a Cloud PBX migration that applies to any business, anywhere. It then adds a separate Luxembourg section covering the items that change in the Grand Duchy and the Greater Region.

Before you start: what a Cloud PBX migration really involves

A Cloud PBX migration is the process of replacing an on-site phone system, an ISDN line, or an older hosted phone service with a phone system delivered over the internet, while keeping your existing numbers and call flows working.
The work splits cleanly into eight phases: discovery, design, provider selection, network preparation, number porting, configuration, pilot, and cutover. A small office of five people can move through them in two weeks. A hundred-seat company with branch offices, custom integrations, and alarm lines may need eight to twelve weeks of planning.
đź“Ś The single most common migration mistake
Treating the migration as an IT project rather than a business project. Cloud PBX touches reception, sales, accounts, after-hours service, fax, alarm panels, lift phones, and payment terminals. If only IT is in the room when call flows are designed, something will be missed. The list of "what depends on the phone line" is always longer than the first draft.

The universal Cloud PBX migration checklist

The checklist below assumes a four to eight week timeline. Compress it if you are smaller, expand it if you have multiple sites or critical compliance constraints.

Phase 1: Discovery and audit (week 1 to 2)

  • Inventory every active phone number, including direct dial numbers (DIDs), fax numbers, and any unused but reserved ranges.
  • Document every call flow on paper: opening hours, IVR menu, queue logic, voicemail routing, after-hours behaviour.
  • List every integration the phone system touches: CRM, helpdesk, billing, calendar, contact centre tools.
  • Identify non-voice services on phone lines: alarm panels, lift emergency phones, payment terminals, door entry, paging.
  • Pull current contracts. Note notice periods, exit clauses, minimum terms, and any porting or release fees.
  • Talk to reception. They know about lines and behaviours no document mentions.
Tip: ask the finance team to pull twelve months of phone bills. Unused lines often appear in the data even when nobody at the office remembers them.

Phase 2: Design (week 2 to 3)

  • Decide your hosting model: pure cloud, or hybrid with a local survival appliance.
  • Define your feature scope: IVR depth, call recording, queues, callback, voicemail to email, app-based working.
  • Build your internal numbering plan: extension length, dialling rules between sites, short codes.
  • Decide your call recording policy: who is recorded, with what consent prompt, retained how long.
  • Map opening hours, holiday routing, and out-of-hours behaviour for every published number.
  • Set roles and permissions: who can change IVRs, who can pull call reports, who can manage users.

Phase 3: Provider selection (week 3)

  • Shortlist two or three providers, including at least one local operator.
  • Send each a written brief based on your discovery and design notes.
  • Ask each to confirm in writing: number portability scope, port timeline, support hours, support languages, SLA.
  • Compare pricing models honestly: per-user, per-channel, included minutes, premium destinations, hardware rental.
  • Request a written go-live plan and a named project contact.
  • Sign the contract only when the porting and cutover plan is in the document, not just the price.

Phase 4: Network and connectivity (week 3 to 4)

  • Estimate bandwidth: plan for around 100 Kbps per concurrent call as a rule of thumb.
  • Configure Quality of Service (QoS) on the LAN and router so voice traffic has priority.
  • Open the firewall ports requested by the provider. Avoid placing the PBX behind aggressive Session Initiation Protocol (SIP) inspection, often called SIP ALG, which is a frequent cause of one-way audio.
  • Plan power: desk phones usually need Power over Ethernet (PoE) switches.
  • Test at least one remote worker on a typical home connection.
  • Plan a backup internet path: a 4G or 5G failover line for the office or for the PBX provider.

Phase 5: Number porting (week 4 to 6)

  • Submit the port request as early as the new provider allows. Porting is the longest-lead item in most migrations.
  • Provide the exact owner details, addresses, and the latest bill from the old operator.
  • Get the port date and time in writing from both the old and new operator.
  • Plan the cutover for a quiet window: outside business hours, ideally a Friday evening or a Saturday morning.

Phase 6: Configuration (week 4 to 6)

  • Provision every user, even the ones who only use a mobile.
  • Build the IVR, call queues, time-based routing, and voicemail trees in the new system.
  • Configure voicemail to email and any transcription you plan to use.
  • Set up CRM and helpdesk integrations, and test click to dial in both directions.
  • Apply your call recording rules and verify the consent message plays before recording starts.
  • Provision desk phones via autoprovisioning where supported. Manual provisioning of more than ten phones is rarely worth the time.
  • Install softphone and mobile apps on a pilot group.

Phase 7: Pilot (week 5 to 6)

  • Run five to ten users in parallel on the new system for one to two weeks.
  • Test 112 emergency dialling from every site and every device type, including softphones.
  • Test inbound calls from real external mobiles to every published number.
  • Test outbound caller ID: the number shown must be the one the customer expects, not a random extension.
  • Test hold, transfer, conference, and barge-in if used.
  • Test fax workflows: most businesses replace fax with email or a dedicated cloud fax service.
  • Keep a written issues log. Close every issue before cutover.

Phase 8: Cutover and the first month

  • Confirm the port slot with both providers forty-eight hours in advance.
  • On cutover day, run a war room with the provider on a separate line.
  • Immediately after the port, call every main number from an external mobile and from a landline.
  • Update your website, email signatures, Google Business Profile, and any printed material with the correct number format.
  • Keep the old system reachable for one to four weeks if possible, in case a hidden device still references it.
  • Cancel old contracts only after the notice period and after the last dependency has been moved.
  • Schedule a thirty-day review to revisit call flows once real call data has accumulated.
đź“… Day-one success criteria, in one line: every customer who calls your main number reaches the right person, and every employee can make outbound calls with the correct caller ID. Everything else can be tuned in the weeks after.

What changes when you migrate in Luxembourg

Most of the checklist above is universal. A few items behave differently in Luxembourg and the Greater Region, and a few extra ones apply only here.

The traditional copper network is already gone

POST Luxembourg has completed the migration of analog and ISDN voice lines onto its All-IP network. The traditional copper telephony network no longer carries voice for business or residential customers. In practice this means most Luxembourg businesses are not migrating from ISDN any more: they are migrating from a first-generation hosted PBX, a vendor-managed IP-PBX, or a Cloud PBX they have outgrown. The checklist still applies, but the ISDN cutover risk that dominates UK and German migration guides is no longer the central issue here.

Number portability is regulated by the ILR

Number portability is the right to keep your existing phone number when you switch operators. In Luxembourg it is mandated and supervised by the Institut Luxembourgeois de RĂ©gulation (ILR).
Luxembourg uses a closed national numbering plan with no geographic area codes. Fixed numbers are eight digits and usually start with 2. Mobile numbers are nine digits and start with 6. Numbers can be ported between any licensed operators, and porting activations are handled within business hours on working days. Allow extra time for block ports of fifty or more numbers, and never plan a port for the eve of a public holiday.

112 emergency calling must keep working

Every Cloud PBX provider serving Luxembourg must support free calls to 112 from every line and every device. Test 112 during the pilot from a desk phone, a softphone, and a mobile app at each site. Confirm with your provider how caller location is transmitted to the emergency services, especially for nomadic users and home workers.

The cross-border workforce

A large share of Luxembourg businesses employ staff who live in Belgium, France, or Germany. Cloud PBX handles this natively because users connect over the internet. Two practical checks: confirm that your provider's softphone and mobile app work cleanly on the home networks your staff actually use, and confirm that international call rates from a Luxembourg number to your most common cross-border destinations are predictable, not metered through a premium gateway.

Multilingual call flows

In Luxembourg, customers often switch between French, German, Luxembourgish, and English in the same call. Plan your IVR with at least two languages, ideally three. Record greetings with native speakers and update them when public holiday dates change each year.

GDPR, call recording, and the CNPD

The Commission nationale pour la protection des données (CNPD) is the data protection authority in Luxembourg. Call recording is allowed, but it requires a clear lawful basis, an informed announcement before recording starts, defined retention periods, and the ability to delete a recording on request. Build these rules into the configuration phase, not after go-live.

Data residency and sector rules

For financial services, insurance, and any business under CSSF supervision, ask your provider for written confirmation of where call data, recordings, and configuration are hosted. EU-region hosting is usually the minimum; Luxembourg or Greater Region hosting may be required by internal policy or by a specific contract clause.

Connectivity options behind the PBX

A Cloud PBX is only as reliable as the internet behind it. Luxembourg has several capable infrastructure operators, including POST, Eltrona, Tango, and Orange. For business-critical sites, plan two internet paths from two different operators, and confirm with your PBX provider how a path failover is handled at the call level.
🇱🇺 What "Luxembourg-specific" really means in 2026
A decade ago, "Luxembourg-specific" meant ISDN, local numbering quirks, and limited cross-border calling options. Today it mostly means three things: handling the cross-border workforce gracefully, designing multilingual call flows, and getting the GDPR and sector-residency questions answered in writing before signing. Everything else is the same migration any European business would run.
⚠️ Items that look optional but rarely are
Backup internet, 112 testing on softphones, an updated emergency address per nomadic user, and a written rollback plan. Each one feels like overhead during planning, and each one saves the project at some point.

After cutover: what to keep checking

A migration is not finished on cutover day. For the first month, plan a short weekly review covering:
  • Call quality complaints by site and by device type.
  • Abandoned and missed call rates compared to the pre-migration baseline.
  • Outbound caller ID correctness on real outgoing calls.
  • Voicemail and recording retention policies running as configured.
  • Any device, alarm, or integration still pointing at the old system.
After thirty days, revisit the IVR and queue design with real call data. The first design is always a hypothesis. The second one is informed by what callers actually do.
đź“š Going deeper on specific steps
Read the dedicated guide on number porting in Luxembourg, see how Microsoft Teams Phone compares to Cloud PBX for Luxembourg SMEs, browse Cloud PBX features to refine your scope, or compare providers active in the Greater Region. Definitions of every term used above sit in the glossary.
đź“… Ready to plan your Cloud PBX migration?
A short conversation with an experienced consultant often saves weeks of planning. The session is free, independent, and takes about twenty minutes.
Book a free consultation | Compare providers | Explore features