Pegasus Opera 3 Migration: SQL SE Readiness, Payroll Risk, and Legacy Workflow Review
Pegasus Opera 3 is still trusted across hundreds of UK SMEs for finance, payroll, nominal and stock — but the platform is changing underneath. The move from VFP-style storage to SQL SE, evolving payroll legislation, and ageing Windows Server estates are pushing organisations to reassess.
The risk in Opera 3 migrations is rarely the financial ledger. It is payroll calendars, year-end timing, bespoke reports, and the small ecosystem of add-ons (CRM, document management, OCR) that have grown around it.
TL;DR
Pegasus Opera 3 migrations live or die on payroll timing, SQL SE readiness, and the bespoke reports around the ledger — not the core finance data. Plan the assessment around those three dependencies first.
System facts
- Vendor
- Pegasus (an Infor company)
- Current platform
- Opera 3 SQL SE / VFP variants in production
- Key risk area
- Payroll deadlines and statutory submissions
- Common add-ons
- CIS, XRL, Document Management, CRM, Web Xchange
- Infrastructure
- Frequently on Windows Server 2012/2016
- Hollinford recommendation
- SQL SE readiness assessment before migration date
Business risk
What this exposes the business to
Payroll continuity
Weekly, fortnightly and monthly payroll cycles cannot slip. A migration window that overlaps a payroll run creates real legal and reputational risk.
Statutory submissions
RTI, P11D, P60 and pension auto-enrolment all have hard deadlines. A migration must preserve audit trails across the switchover, not just the live ledger.
Reporting parity
Finance and management rely on a handful of XRL/Excel reports that have evolved for years. If the successor system can't reproduce them, adoption stalls.
Add-on compatibility
Document management, OCR, CRM and Web Xchange integrations may not have a clean equivalent on the target platform.
Technical risk
What is fragile under the hood
SQL SE readiness
Moving from VFP-style storage to SQL SE involves data conversion, performance tuning and connection-string updates across every add-on. It is not a flip-the-switch upgrade.
Windows Server lifecycle
Many estates still sit on Windows Server 2012 or 2016. Opera versions, .NET runtimes and SQL editions all need to line up with a supported OS.
XRL / Excel reports
Reports authored in XRL pin themselves to specific connection details, columns and stored procedures. They almost always need rebuilding rather than copying.
Custom scripts and triggers
Bespoke posting rules, custom triggers or third-party add-ons can lock you to a specific Opera version unless they are inventoried before the project starts.
Hidden dependencies
The things that break a migration on the day of cutover
CIS, payroll and HMRC submissions
Submission logs, certificates, and historic returns need to remain accessible after cutover for at least the statutory retention period.
Web Xchange and remote workers
Field staff and remote users may rely on Web Xchange or remote desktop sessions. Their workflows have to be re-tested on any new platform.
Stock, BOMs and works orders
Manufacturing and stock modules tie into supplier price files, BOMs and routing rules that often live partly in Opera and partly in spreadsheets.
Bank reconciliation imports
Bank statement formats, supplier payment files and BACS templates need to be reproduced exactly on the new system to avoid finance team rework.
Decision matrix
Stabilise, integrate, migrate or replace?
| Option | When it fits | Main risk |
|---|---|---|
| Stabilise on Opera 3 | Vendor still supports your version, infrastructure is healthy, no immediate pressure to change. | Defers the problem; Windows Server and SQL editions still age out underneath. |
| Upgrade Opera 3 + move to SQL SE | Committed to staying on Opera and want a supported, modern foundation. | Migration of add-ons and XRL reports is often underestimated. |
| Replace with mid-market ERP | Stock, manufacturing or multi-entity needs are pushing beyond Opera's comfort zone. | Larger programme; needs explicit payroll and reporting workstreams. |
| Split: keep payroll, replace ledger | Payroll works well and you want to reduce migration scope on the first phase. | Integration between successor finance system and Pegasus payroll needs proper design. |
Recommended first step
Start with a Legacy Health Check
Two weeks, fixed price, no obligation to use Hollinford for delivery. You get an inventory, a risk register, a prioritised roadmap and an executive summary you can use with the board or to brief another supplier.
- Full inventory of dependencies, integrations and reports
- Risk register rated by impact and likelihood
- Prioritised modernisation roadmap with options
- Executive summary written for non-technical decision-makers
Engineer's note
On Pegasus Opera 3 estates, the first artefact we build is a payroll calendar overlaid on the proposed migration plan. That single view tends to remove half the proposed cutover dates immediately, because they collide with a payroll run, a HMRC deadline or pension submission.
The second artefact is a complete list of XRL/Excel reports with their owners. In most estates we look at, four or five reports are doing the heavy lifting for the whole management team — and almost none of them are documented.
Frequently asked questions
Is Pegasus Opera 3 being discontinued?+
Pegasus Opera 3 is still actively supported and updated. The reason most clients ask the question is not end-of-life, but the cumulative cost of ageing infrastructure, bespoke reports and add-ons that no longer fit how the business runs.
What does SQL SE mean for our Opera migration?+
SQL SE moves Opera onto a SQL Server back-end instead of the older file-based storage. It improves performance, integration and reporting potential but it is a real migration: data conversion, add-on compatibility and connection-string changes all need to be planned.
How do we protect payroll during a migration?+
By scheduling around payroll, not through it. The migration plan should align with payroll calendars, statutory deadlines and pension cycles, and include parallel runs and rollback windows that the payroll team is comfortable with.
Can we keep Pegasus payroll and replace only the ledger?+
Yes, and for some businesses it is the lowest-risk path. The catch is that the integration between the new finance system and Pegasus payroll has to be designed explicitly, not assumed.
Related sectors
Ready to map your legacy system risk?
Book a Legacy Health Check and get a clear, prioritised picture of what to modernise first.