3CX V20: what’s new, Update 10 and migrating from V18

The short answer: if your 3CX system is still on V18, you need to migrate, because that version is no longer maintained and the apps no longer connect to it. If you are already on V20, stay current on the latest stable release, which is Update 9 at the time of writing, and test Update 10 separately: it is still at release candidate stage. The upgrade itself takes only a few clicks; the preparation is what makes the difference: system owner, internal DNS, departments, office hours and permissions.

This guide relies on documentation and the change log published by 3CX, consulted on 5 November 2026. It complements our article on why 3CX works so well for SMBs and is written for those already running a system. ALLSAFE SOLUTIONS, a 3CX Bronze Advanced Certified partner in Casablanca, carries out these migrations with its own engineers.

Where 3CX stands today

V20 Final dates from February 2024, and 3CX has shipped regular updates since. Here are the useful milestones, taken from the official change log.

Version	Build	Date	Key point
V20 Final	20.0.0.1620	February 2024	New architecture, Debian 12, unified admin console
Update 2	20.0.2.715	July 2024	Anti-Hacking module added during this release cycle
Update 7	20.0.7.1057	October 2025	Memory leak fixes and protection against queue loops
Update 8	20.0.8.1109	February 2026	New OpenAI models; Update 8A in March adds protection against recent SIP attacks
Update 9	20.0.9.995	June 2026	Latest stable release, nginx embedded directly in the installation
Update 10 RC2	20.0.10.1765	October 2026	Test build, final fixes before the final release

The change log also lists a proactive security hotfix from June 2026, released for both Update 8 (build 20.0.8.1131) and the upcoming Update 9. A system left on an earlier release does not get that fix, which is a concrete reason not to let updates pile up.

What V20 changed compared with V18

V20 is not a routine update: 3CX describes its architecture as fully redesigned. Five changes have a direct day-to-day effect.

• One console, one address. The admin console joins the Web Client, on the same address and with the same login. The /webclient/ suffix disappears, which means reinstalling the web app (PWA) on workstations.
• No more invisible accounts. The root admin and hosting admin accounts, which left no trace in logs, are gone. You log in with the system owner account.
• Departments replace groups. They hold their own office hours, holidays, time zone and language, and form the basis for permissions. If you do not want them, everything can stay in the default department.
• A native Windows softphone. It replaces the old desktop app and is deployed through the Microsoft Store, with updates independent of the PBX. See our guide to the 3CX mobile, web and Windows apps.
• Stronger security. Debian 12, two-factor authentication, Microsoft or Google sign-in, Web Client restriction by IP address. These settings still need to be enabled and checked: follow our guide to securing a 3CX system.

V20 also brings a new call manager, new queue strategies, call processing scripts, a call control API and VoIP quality monitoring. For a customer service team, read these alongside our article on running a call centre with 3CX.

Update 10: what is coming, and what can wait

3CX published the Alpha on 30 July 2026 and RC2 on 29 October, advising evaluation on a test system. The announced additions are numerous:

Area	Addition announced by 3CX	For whom
AI	Standalone AI Server, on Apple Silicon Mac or on Debian with an NVIDIA GPU	Companies wanting transcription processed in-house
AI	Customer Service AI Agent, alongside the Receptionist and Personal Assistant	Front desks with many repetitive questions
Openness	Native MCP server to connect ChatGPT, Claude or Gemini, with OAuth and subject to the user’s role	Administrators, reporting
Openness	Programmable Extensions and AI Call Scripts	Custom development projects
Phones	Vendor firmware deployable per model or per phone, custom templates, new Phones page	Mixed fleets, office moves
Daily use	Outbound number choice, quick audio conferencing, pop-out dialer	Sales teams, multi-number teams
Permissions	Separate permissions for reports and recordings, audit of recording downloads	Compliance, see our article on call recording
Integration	Native Odoo integration, no middleware	Companies on Odoo, see 3CX and CRM

Two points deserve attention before installing it.

If you already use the 3CX AI Server, Update 10 requires reinstalling it. 3CX recommends configuring and testing a temporary cloud provider for transcription, switching during a quiet period, and then checking recordings from the transition window. The vendor also strongly recommends a clean Debian install if you reuse the machine.

If you use a free 4SC licence, 3CX says previously announced restrictions begin to take effect, starting with new IP phone configuration. The console also shows the maximum number of extensions for the licence and blocks new users once the limit is reached. Check your sizing with our guide to choosing a 3CX licence.

Our advice for production: stay on Update 9 and wait for the final Update 10, unless you have a specific need to validate on a test system. The move then happens from Admin Console, System, Updates, installing the offered updates in sequence.

Moving from V18 to V20: the prerequisites

V18 Update 9 is the starting point for the upgrade. Before clicking, four checks prevent most blockers.

1. Assign a system owner. This is the account you will log in with after the migration. Its extension needs an email address not used by any other extension. 3CX warns that upgrading without a system owner causes major issues.
2. Check resources. At least 2 vCPUs, 2 GB of RAM and 5 GB of free disk space. According to 3CX, too few cores is the top reason an upgrade does not start. Its sizing recommendations are higher than this minimum, with 4 GB of RAM from the smallest profile.
3. Clean up the server. No third-party software, no added package sources, and uninterrupted internet access to repo.3cx.com and deb.debian.org. A monitoring or remote administration agent on the server can also interfere with the process.
4. Prepare split DNS. For an on-premises system, the PBX name must resolve from both the local network and the outside. That means an internal DNS server or a firewall capable of hairpin NAT. 3CX acknowledges that very small networks may have to replace their router or move to the cloud, so check this on a basic operator router. Our comparison of cloud or on-premises phone systems helps you decide.

Three migration paths

Situation	Method	Watch out for
V18 Update 9 on Debian, clean server	Upgrade button in the console	Goes through Debian 11 then 12, service unavailable during the process
Modified server, or hardware replacement	Backup, fresh install, restore	Keep the domain name and licence, test before moving lines
V18 on Windows	Backup, uninstall, install V20, restore	No in-place upgrade; first check that your edition allows V20 on Windows

3CX’s documentation covers these steps fairly briefly, and its guide dates from June 2024. For an older system, especially on Windows or with an expired licence, check the situation with your partner before uninstalling anything.

The migration, step by step

1. Choose the window. 3CX states a duration from 10 to 15 minutes up to an hour or more, depending on the machine, installation size and connection. The system is unavailable during that time, so plan it outside office hours.
2. Back up. Take a full backup, download it off the server, and take a virtual machine snapshot if possible.
3. Start the upgrade, then leave the system alone. 3CX sends an email at the end with the result: aborted, failed or successful.
4. Test straight away. Inbound and outbound calls on each line, desk phone, mobile app, softphone, queue, voicemail, recording.

If it fails, 3CX advises fixing the requirements and running it again, then, if that is not enough, restoring the backup to a new system.

After the migration: settings to revisit

This is where the unpleasant surprises hide, because the system appears to work.

• Office hours. The old global hours are copied to each department. 3CX’s guide states that calls are treated as in-office until destinations are configured, so a night-time call may no longer reach the intended voicemail. Test outside office hours.
• Permissions. Rights are reset to each role’s defaults, and the guide states that roles cannot be customised in V20. Review your managers and supervisors.
• Call visibility. Users see only their own department’s calls unless you grant access to other departments.
• Queues, IVRs and ring groups. Place them in the right department, or in the default one.
• Workstations. Deploy the Windows softphone in place of the old desktop app, or the web app, and update the mobile apps.
• Call quality. Use the new quality monitor to detect network problems, and go through our list of mistakes that ruin call quality.

Checklist to keep at hand

• Exact version and build noted before you start.
• System owner assigned, with a unique email and verified access.
• At least 2 vCPUs, 2 GB of RAM and 5 GB free, with no third-party software.
• Split DNS tested from the local network.
• Full backup copied off the server, plus a virtual machine snapshot.
• Window outside office hours, users informed.
• Written test plan: lines, phones, apps, queues, voicemail, recording.
• Hours, permissions and visibility reviewed department by department.
• Next licence expiry date noted.

How we work

We start with an audit of your system: version, hosting, licence, lines, phones and network. We then prepare the migration on a backup, with a rollback plan, carry it out outside office hours and check every line and app. Our engineers review hours, permissions and security settings, and the system stays monitored 24/7, with critical incidents handled in under 15 minutes.

To place this project in your wider plans, see our IP telephony in Morocco offer, then request your free phone system audit: free initial audit, reply within 24 business hours, from Casablanca and across Morocco.