Genie Desktop and Gentu — What Melbourne Practices Need to Know
6 July 2026 · 7 min read
If your specialist practice runs Genie desktop, you have probably noticed that Magentus — the company that now owns Genie Solutions — is pushing hard toward Gentu, their cloud-based successor. Emails, webinars, migration guides. The messaging is clear: Gentu is where Magentus is investing. What is less clear, for most practice managers, is what this means for your day-to-day operations right now, and what your IT environment needs to look like to support either platform.
Genie Desktop Is Not Going Away Tomorrow
The first thing worth saying plainly: Genie desktop is not end-of-life. Magentus continues to release updates, and there is no published sunset date for the desktop product. Practices running Genie on a well-maintained server can continue doing so without urgency. The pressure to move is commercial, not technical — Magentus's growth strategy is Gentu, and they will invest accordingly. But supported and actively developed are two different things, and Genie desktop remains the former.
What has changed is the trajectory. Feature parity between Genie desktop and Gentu is narrowing in Gentu's favour. New integrations — particularly around telehealth, patient-facing booking, and cloud-based pathology — are being built for Gentu first. If your practice relies heavily on any of these capabilities, the migration conversation becomes more relevant sooner.
What Your IT Environment Needs for Genie Desktop Right Now
Running Genie desktop well in 2026 requires a server environment that is actively maintained, not one that was set up five years ago and left alone. The most common IT gaps we see in Genie desktop practices are:
Windows Server currency. Genie desktop runs on Windows Server, and older versions (2012 R2, 2016) are either out of extended support or approaching it. An unsupported server OS is a compliance and security liability — the Australian Privacy Act and RACGP accreditation both expect software to be maintained and patched. If your Genie server is running a deprecated OS, that needs to be on your IT roadmap.
SQL Server maintenance. Genie's database runs on Microsoft SQL Server. This component requires regular maintenance — index rebuilding, statistics updates, transaction log management — that most practices have never done because nobody told them it was necessary. A neglected SQL Server database will degrade in performance over time and become increasingly difficult to restore cleanly from backup.
Backup verification. As covered elsewhere, Genie backup failures are common and often silent. A Genie desktop environment should have a nightly verified backup to at least two destinations, with documented restore tests every six months. This is not optional under the Australian Privacy Act — it is an obligation.
Antivirus exclusions. Genie's installation directory and database ports need to be excluded from real-time antivirus scanning. This is a well-documented requirement that is routinely missed in practices managed by generalist IT providers, and it causes intermittent performance issues that are difficult to diagnose without knowing to look there.
What a Migration to Gentu Actually Involves from an IT Perspective
If your practice is planning to move to Gentu — or evaluating it — the IT components are often underestimated in the project timeline.
Data migration. Magentus provides a data migration pathway, but it is not a simple export-import. Patient records, appointment history, clinical notes, and financial data all need to transfer correctly, and the migration should be validated against the source data before you decommission the Genie server. Your IT provider should be involved in this validation step, not just the practice manager.
Server role changes. Once you are on Gentu, your server's role changes significantly. You no longer need to run a local SQL Server instance for the clinical database — Gentu is cloud-hosted. Your server becomes primarily a file server and workstation management point. Some practices take this opportunity to simplify their infrastructure; others maintain the server for other functions (accounting software, document management). Either is valid, but it needs to be a deliberate decision, not a surprise.
Internet dependency. Gentu is cloud-based, which means your clinical operations become dependent on internet connectivity in a way they were not with Genie desktop. Before migrating, your internet connection should be assessed for reliability and failover. A practice with a single ADSL or NBN connection and no backup should address that before moving clinical software to the cloud — not after their first outage.
Workstation readiness. Gentu is browser-based, which means workstation requirements shift from local software installation to a supported browser and adequate RAM. Most modern workstations handle this comfortably, but older machines — particularly those running Windows 10 on spinning hard drives — may need assessment before the migration date.
Supporting Both in Parallel During Transition
Some practices run Genie desktop and Gentu in parallel during a transition period, particularly those migrating site-by-site in a multi-location group. This is manageable but requires your IT provider to understand both environments. Data written to Genie desktop during the transition period needs to be accounted for in the final migration, and staff need to know clearly which system to use for which tasks.
The Bottom Line
If you are running Genie desktop today, the right action is not panic migration — it is ensuring your current environment is properly maintained while you plan the transition at a pace that suits your practice. The IT components of that plan — server health, backup integrity, network readiness, workstation assessment — are where a specialist healthcare IT provider adds the most value. Those decisions should not be made by Magentus's migration team alone.
Whether you stay on Genie desktop for another two years or move to Gentu in the next six months, your IT environment needs to be in good shape either way. That is the part we can help with.
Not sure where your practice stands?
A Compliance Gap Assessment covers backup and DR posture, access controls, and compliance documentation — a written report with a prioritised roadmap.