Legacy Software Modernisation for Singapore SMEs: Options and Costs

Two support dates have passed in the last year for software many SME offices still run:

• Windows 10 reached end of support on 14 October 2025. Organisations can buy Extended Security Updates for a maximum of three years, priced per device and doubling in price each year.
• SQL Server 2016 reached the end of extended support on 14 July 2026, with paid security updates available into 2029.

Unsupported software is also a data protection question. The PDPC's guide to data protection practices for ICT systems recommends applying security patches promptly, and software that no longer receives patches cannot meet that standard. If the old application holds customer or employee personal data, the PDPA's protection obligation applies to it like any other system.

Legacy systems in small offices tend to fall into a handful of shapes:

• A Microsoft Access database on a shared drive, with forms several staff open at once.
• A Visual Basic 6 or early .NET Windows application written by a developer who has since moved on.
• An Excel workbook with macros that has quietly become the costing or quotation system.
• A PHP web application on an old PHP version, hosted on a server nobody patches.
• A packaged product whose vendor stopped releasing updates, with data you can still export.

Each shape has its own easiest exit. Access and Excel systems usually hold simple data but hide business rules in formulas. Old Windows applications often talk to printers, scanners or weighing scales. Old web applications usually have the cleanest path to a modern stack.

Keep and contain

Isolate the machine, restrict who can reach it, back it up and plan the exit. Right only when the system will be retired within a year or so.

Upgrade in place

Move to a supported version of the operating system, database or framework while keeping the application's design. Good value when the logic is correct and the platform is the problem.

Wrap with an API or web front end

Keep the old database and core logic, add an API layer and a new web or mobile front end on top, then replace the old core over time. Useful when staff need remote access but the logic is too risky to touch all at once.

Rebuild as a web or desktop application

Write the system again on a current stack, module by module. Choose a web application when users work in different places and on different devices. Choose a desktop application when work must continue without internet or depends on local hardware. Our SchoolBill Windows app, built for a multi-branch private school in India, keeps taking student entries when the internet drops and uploads them once it returns; the same pattern suits shop counters, warehouses and clinics.

Replace with a packaged product

For accounting, payroll or HR, a SaaS product may beat any rebuild. Budget for data migration and retraining, and for integration with whatever you keep.

The decision rule

Upgrade in place when the system works and the platform is the only problem. Wrap it when you need remote access quickly and cannot risk touching the core. Rebuild when every change is slow or the logic no longer matches how you work. Replace when the process is standard and not where you compete.

What drives the cost

We will not quote SGD figures here, because a number means little without seeing the system. These factors move the price most:

• The number of screens, reports and printed documents to recreate.
• Data volume and quality, and how many years of history must come across.
• Integrations with accounting software, banks, e-commerce platforms or government portals.
• The number of user roles and branches.
• Offline operation or hardware connections.
• How long old and new must run in parallel.
• Whether any documentation exists, or the rules must be read out of the code.

To get a quote you can rely on, give a vendor screenshots of every screen, samples of every report, a copy of the database structure and a list of who uses what. A vague brief produces a vague quote with a large risk margin built in.

Grants: what EDGE changes, as of October 2026

Enterprise Singapore has folded the Productivity Solutions Grant (PSG), Enterprise Development Grant (EDG) and Market Readiness Assistance (MRA) into one scheme. According to the EDGE grant FAQ, EDGE launched on 30 September 2026, and no new applications are accepted under the old schemes after that date. The points that matter for a modernisation budget:

• SMEs can receive up to 50% support, or up to 70% for internationalisation and sustainability activities; non-SMEs up to 30%.
• Each company has an annual grant cap of S$100,000 across eligible activities, resetting every 1 April.
• Within that cap, up to S$30,000 can go to single-function digital solutions, integrated enterprise systems and pre-scoped equipment.
• Applicants must be registered in Singapore with at least 30% ownership by Singapore citizens or permanent residents.
• An application is not supported if you have started work or paid any deposit to a vendor before submitting it.

Whether a custom modernisation project qualifies, and under which category, depends on its scope. Confirm with Enterprise Singapore before you sign anything, and do not let any vendor take a deposit until your application is in.

• Freeze and copy. Take a full backup and set up a read-only copy for analysis.
• Inventory. List every screen, report, export and scheduled task, and who uses each.
• Map the data. Old field to new field, with a decision recorded for every field you drop.
• Build in phases. Start with the module that causes the most pain, not the easiest one.
• Rehearse. Migrate a copy of the data at least twice and reconcile counts and totals.
• Run in parallel. Keep the old system available, read-only if possible, for an agreed period.
• Retire. Archive what you must keep for your retention periods, then switch the old system off.

Singapore is 2.5 hours ahead of India, so a 10:00 SGT meeting is 07:30 in Greater Noida, and nearly all of your working day overlaps with ours. DipanshuTech has 10+ years of work, 963+ projects delivered and 63+ developers. A relevant example is our own consolidation work: ERPSetu was built by merging 17 of our earlier ERP codebases into one product, now live with 84 of 84 automated gates passing. It was built for Indian SMEs, but untangling overlapping old code without losing behaviour is the same job. Our legacy modernisation service starts with discovery, then a written scope and a fixed quote, with working software on a staging server every two weeks and source code in your company's name.

Can we keep using Windows 10 PCs?

They keep working, but without security fixes unless you pay for Extended Security Updates. Use that time to move the applications that keep you on Windows 10.

Is it cheaper to upgrade or to rebuild?

Upgrading is usually cheaper up front. Rebuilding pays off when you keep paying for slow changes, workarounds or manual re-entry.

Can EDGE fund a project built by an overseas developer?

Check with Enterprise Singapore for your specific project and category before signing. The rules on eligible costs and vendors are set by the agency, not by the developer.

How long does a modernisation take?

A single small application can often move in 2–4 months. Larger systems are best done in phases over 6–12 months, with each phase delivering something staff can use.

If an old system is holding your business back, discuss your project with us. Send screenshots and a list of users, and after a short discovery call we will send a written scope and a fixed quote.