Can you keep Pegasus Opera and modernise everything around it?
Yes, on whichever edition of Opera 3 you're running. It stays your system of record while a bespoke, real-time interface gets built on top of it — no rip-and-replace, no accounting migration, and nothing lost from the setup your business already runs on. This is what Sysgraft calls a graft: a precise join between a new intelligent layer and the systems you already own.
Should you replace Pegasus Opera, or build around it?
For most £1.5m–£20m+ UK businesses, the honest answer is: build around it.
Pegasus Opera is usually not the problem. It's an accounts and business management system, and it does that job well. The problem is that it was never designed to be a live, cross-business dashboard for leadership. The frustration leaders feel ("why can't I see margin in real time?", "why does month-end still take a week?") isn't a reason to tear Pegasus Opera out. It's a reason to add a layer it was never meant to provide.
Ripping out a working accounts system to solve a reporting and visibility problem is one of the most expensive mistakes a mid-market business can make: months of migration, retraining, data risk, and disruption — to fix something a graft would fix without any of it.
What connecting to Pegasus Opera actually involves
On Opera 3 SQL SE, Pegasus provides its own Data Connector — an OData-based route built for exactly this, and the same one Pegasus uses for its own Power BI and Excel reporting. One thing worth confirming early: which edition of Opera 3 you're on. The Data Connector route applies to SQL SE specifically — if you're on an older edition, that's a five-minute question to settle at discovery, not a blocker, though it may mean a different route (third-party Opera API tooling exists for older editions too).
Either way, that confirmation happens before a price is quoted, not after a build has started.
Common questions about modernising around Pegasus Opera
Can custom software sit on top of Pegasus Opera?
Yes. On Opera 3 SQL SE, Pegasus provides its own Data Connector — an OData-based route built for exactly this, and the same one Pegasus uses for its own Power BI and Excel reporting. A bespoke interface can draw live data through it and present it alongside data from your CRM and other systems, giving leadership one real-time view without changing how Opera itself works.
Can I get a real-time dashboard from Pegasus Opera without replacing it?
Yes. On Opera 3 SQL SE, a dashboard can read live through the same Data Connector route Pegasus uses for its own reporting, sat alongside your other systems.
Is Pegasus Opera the problem, or our processes?
Often, neither is fully the culprit. Pegasus Opera runs your accounts the way it's meant to, whichever edition you're on — the real issue is usually that it was never designed as a cross-business dashboard, and that's solvable without replacing anything.
Can I connect Pegasus Opera to my CRM and see both in one place?
Yes. Grafting an interface across Pegasus Opera and your CRM lets customer, sales and accounts data appear together — the single view that neither system gives you alone.
Does keeping Pegasus Opera limit what AI can do later?
No. What limits AI usefulness is fragmented data, not which accounts system — or which Opera 3 edition — you run. Once that data is joined into one accessible place, AI features have something coherent to work with. Keeping Pegasus Opera doesn't hold that back.
Modernising isn't migrating
The software industry has trained businesses to believe that "modernising" means a large, disruptive replacement project. It doesn't have to. Grafting a new layer onto Pegasus Opera is modernisation without the migration — you move forward on visibility and capability while Pegasus Opera keeps working, whichever edition you're actually on.
See how the whole process works, step by step →
Get your AI Exposure snapshot Find out where your real constraint is — most often it isn't AI, and it isn't Pegasus Opera