Pegasus Opera 3 Visual FoxPro End of Life: Your Guide

Pegasus has announced that Opera 3 Visual FoxPro will reach end of life on 30 December 2028. But what does that actually mean for businesses still using the software, and what should you be doing now?

If your business relies on Pegasus Opera 3 for accounting, payroll, stock control or day-to-day operations, hearing that your software is approaching end of life can understandably raise some concerns.

Will your system stop working? Will you need to replace it? What happens to your support? And how much time do you have to make a decision?

The good news is that there's no need to panic or rush into an expensive software change.

However, there are some important things to understand and decisions worth planning for.

In this guide, we'll explain what's changing, what the announcement means for your business and the options available to help you move forward with confidence.

Is Pegasus Opera 3 being discontinued?

No, Pegasus Opera 3 isn't being discontinued entirely. The end-of-life announcement specifically affects the version of Opera 3 built on Microsoft Visual FoxPro technology.

Pegasus Opera 3 has been a trusted accounting and business management system for many years, helping organisations manage their finances, payroll and operational processes.

However, the Visual FoxPro technology underpinning the older version is now considered legacy technology.

Microsoft ended support for Visual FoxPro in January 2015, and as operating systems, security requirements and business technologies continue to evolve, maintaining older software becomes increasingly difficult.

As a result, Pegasus has confirmed that Opera 3 Visual FoxPro will reach end of life on 30 December 2028.

Importantly, businesses using Opera 3 still have options, including moving to the newer, SQL-based version of the software.

What does the December 2028 end-of-life date actually mean?

The most important thing to understand is that your Opera 3 Visual FoxPro system won't automatically stop working on 30 December 2028.

However, the level of ongoing software maintenance and support available from Pegasus will change.

According to Pegasus's customer announcement, after this date, the Visual FoxPro version will no longer receive compliance updates, including those needed to meet changing legislation.

These could include important updates relating to:

• Payroll legislation and statutory requirements
• VAT returns and related processes
• Changes to financial and regulatory reporting requirements
• Other compliance-related functionality within Opera 3

For businesses that rely on Opera 3 to manage these processes, this is particularly important.

Even if your software continues to operate as it does today, it may become increasingly difficult to keep certain processes compliant as legislation changes.

That's why it's worth reviewing your options before the deadline rather than waiting until your business encounters a problem.

Can you continue using Pegasus Opera 3 Visual FoxPro until 2028?

Yes. Businesses can continue using their existing Opera 3 Visual FoxPro systems while planning their longer-term approach, provided the software remains suitable for their requirements.

However, there are a few things worth considering.

1. Ongoing support may become more expensive

As older software becomes more difficult to maintain, supporting it requires increasingly specialist technical knowledge and resources.

Pegasus has announced that it will introduce a Legacy Support Supplement for customers continuing to use the Visual FoxPro version of Opera 3.

This additional charge will take effect at the customer's next support contract renewal, according to the announcement.

It's therefore worth reviewing your existing support arrangements and understanding how any changes might affect your future costs.

2. Compatibility could become more challenging

As Microsoft Windows, server environments and other business technologies evolve, older software can become harder to maintain.

You may eventually encounter compatibility limitations when replacing computers, upgrading servers or introducing other systems.

Although these issues won't necessarily affect every business immediately, they should form part of your longer-term IT planning.

3. Compliance updates will eventually stop

Perhaps the most significant consideration is the end of compliance updates after December 2028.

For businesses using Opera 3 for payroll, VAT processing or other legislation-dependent activities, this creates a clear reason to review their future software arrangements.

The aim shouldn't be to make an immediate decision out of concern, but to ensure you've got enough time to make an informed one.

What are your options if you're currently using Opera 3 Visual FoxPro?

The right decision will depend on how your business uses Opera 3, what functionality you rely on and whether your current system is meeting your needs.

There isn't necessarily one answer that suits everyone.

Here are three options worth exploring.

Option 1: Upgrade to Pegasus Opera 3 SQL SE

For many businesses, upgrading to Pegasus Opera 3 SQL SE could be a sensible next step.

Opera 3 SQL SE is built on Microsoft SQL Server rather than the older Visual FoxPro database technology.

It provides a more modern technical foundation while retaining much of the familiar Opera 3 experience that existing users already know.

This can make it an appealing option for businesses that are generally happy with Opera 3 and don't want to replace an accounting system that works well for them.

Potential benefits include:

• Familiarity: Continue using an Opera 3 environment without introducing a completely different accounting system.
• Improved data management: Benefit from the SQL Server database architecture.
• Better reporting opportunities: Explore more flexible reporting and access to business information.
• Longer-term development: Move to the edition Pegasus is focusing its ongoing product development around.
• Business continuity: Retain established accounting processes, subject to reviewing compatibility, existing functionality and any customisations.

Of course, an upgrade still requires planning.

Your existing data, integrations, bespoke reports and operational processes should all be assessed before making the move.

But for businesses that want to continue with Opera 3, SQL SE is certainly worth considering.

Option 2: Review whether another accounting or ERP system would suit your business better

An end-of-life announcement can also be a useful opportunity to assess whether your current software is still the right fit.

Your business may have changed significantly since Opera 3 was first implemented.

Perhaps you're managing more companies, handling higher transaction volumes, relying on manual workarounds or finding that your reporting requirements have become more complex.

If that's the case, it might be worth exploring alternative accounting or ERP solutions.

However, replacing an established system isn't something to undertake lightly.

A new solution should offer clear benefits that justify the cost, time and disruption involved.

If Opera 3 is still doing everything your business needs, replacing it with an entirely different system may not be necessary.

The important thing is to review your requirements properly before making that decision.

Option 3: Continue with your current system while developing a transition plan

Not every business will be ready to upgrade immediately, and that's understandable.

You might have other projects underway, budget considerations or operational reasons for delaying a migration.

For some organisations, continuing with Visual FoxPro in the short term while preparing for a future change could be a reasonable approach.

If you choose this option, we'd recommend having a clear plan covering:

• Your current version of Opera 3 and the modules you use
• The compatibility of your existing IT infrastructure
• Your support arrangements and any additional legacy support costs
• Payroll, VAT and other compliance requirements
• The potential risks of continuing beyond December 2028
• A realistic timescale and budget for moving to a supported platform

The key is to make a deliberate, informed decision rather than simply leaving things until the deadline approaches.

How difficult is it to upgrade from Opera 3 Visual FoxPro to SQL SE?

This is one of the most common concerns when businesses consider an accounting software upgrade.

After all, your Opera 3 system might hold years of financial information, customer records, transaction history and important business processes.

Naturally, you'll want to know what happens to that information and how much disruption an upgrade might cause.

Fortunately, Pegasus provides a migration process for moving existing Opera 3 data to SQL SE.

However, the complexity of your upgrade will depend on several factors, including:

• The version of Opera 3 you're currently using
• The number of companies and users within your system
• The modules and functionality you rely on
• Any bespoke developments, integrations or reporting requirements
• The condition and structure of your existing data
• Your current server and IT environment

A well-planned migration should begin with reviewing your existing setup, understanding any potential challenges and establishing what needs to happen before the move.

Testing is particularly important, especially if your business relies heavily on Opera 3 for payroll, stock management or financial reporting.

And while upgrading will involve some preparation, moving to SQL SE may be considerably less disruptive than implementing an entirely new ERP system.

What should your business be doing now?

December 2028 might seem some way off, but it's worth starting the conversation sooner rather than later.

You don't need to make an immediate software purchase or commit to a migration project.

Instead, we'd recommend taking five practical steps.

Step 1: Confirm which version of Opera 3 you're using.

Not sure whether your business uses Visual FoxPro or SQL SE? Start by checking with your IT team or existing Pegasus support partner.

Step 2: Review how your business relies on Opera 3.

Identify the processes, departments and integrations that depend on your accounting system. Pay particular attention to payroll, VAT and other time-sensitive functions.

Step 3: Understand your current support arrangements.

Find out when your support agreement renews, whether a Legacy Support Supplement will apply and what assistance you can expect as the end-of-life date approaches.

Step 4: Explore your options before committing to a solution.

Whether you're considering SQL SE, reviewing another ERP system or remaining on your existing version temporarily, understanding the alternatives will help you make a more confident decision.

Step 5: Build a realistic plan.

Consider the time needed for reviewing your requirements, preparing data, testing, training and completing any necessary migration.

Planning early gives you greater control over the process and helps reduce the likelihood of a rushed decision later.

Frequently asked questions about Pegasus Opera 3 end of life

When is Pegasus Opera 3 Visual FoxPro reaching end of life?

Pegasus has announced an end-of-life date of 30 December 2028 for Opera 3 Visual FoxPro.

Will Pegasus Opera 3 stop working after December 2028?

Not necessarily. Your existing software won't automatically stop functioning on that date. However, Pegasus has confirmed that compliance updates for the Visual FoxPro version will no longer be provided after the deadline.

Will I have to replace Pegasus Opera 3?

Not necessarily. Businesses using the Visual FoxPro version can explore upgrading to Opera 3 SQL SE, which retains the familiar Opera 3 environment while using a newer database platform.

Can I upgrade from Opera 3 Visual FoxPro to SQL SE?

Yes. Pegasus provides a migration route from Opera 3 Visual FoxPro to Opera 3 SQL SE. The work involved will depend on your existing configuration, data, modules and integrations.

Will my existing Opera 3 data be transferred?

Pegasus provides data migration tools for moving existing Opera 3 company information to SQL SE. However, your data, associated files, bespoke developments and other dependencies should be reviewed and tested as part of the migration process.

Can I change my Pegasus Opera 3 support partner?

Yes. If you're unhappy with your current support arrangements or would like access to additional expertise, you can explore working with another Pegasus partner. It's important to review your current contract and the arrangements needed for a smooth support handover.

The most important thing? Make the right decision for your business.

When a business-critical system approaches end of life, it's natural to feel under pressure to act.

But the right response isn't necessarily to replace your software as quickly as possible.

It's to understand what's changing, assess how it affects your organisation and make a practical plan that protects your business.

For some businesses, upgrading to Opera 3 SQL SE will be the natural next step.

For others, reviewing alternative systems or continuing with their existing setup for a defined period may make more sense.

Whatever your situation, you have time to explore your options and make an informed decision.

And the sooner you start planning, the more flexibility you'll have.

Need some guidance on your Pegasus Opera 3 options?

At The HBP Group, we've been working with Pegasus systems for over 30 years, helping businesses get the most from their accounting and ERP software.

Whether you're looking for ongoing support for your existing Opera 3 system, considering an upgrade to SQL SE, or simply want a second opinion on your options, our experienced team can help.

You don't need to be an existing customer, and you don't need to have already decided to upgrade.

We're happy to start with a conversation about your current setup and what makes the most sense for your business.