When a legacy system becomes a risk to the agency
Most legacy systems still work. The risk is in everything around them: a financial or operational system near end of life, an application that depends on one retiring person and can’t safely be maintained or extended, critical work scattered across disconnected tools, or spreadsheet-era processes under audit scrutiny.
Replacing a core system carries real risk too, and most of that risk traces back to the partner. Implementations stall when the vendor doesn’t understand procurement, underestimates data migration, or leaves nothing documented for the staff who come after. Our delivery process is built around those failure points.
Replace, consolidate, configure, or extend: choosing the right path
A legacy system doesn’t always need a custom replacement. Choosing the path is part of discovery, and we recommend the approach that fits the problem.
Configure a commercial product when the workflow is ordinary and a product already does the job. Aging financial and operational systems, such as Microsoft Dynamics GP and Great Plains or older Sage, are often candidates for cloud ERP. We’re building our Acumatica practice for agencies evaluating cloud ERP. See Acumatica ERP implementation for public agencies.
Build a custom replacement when the process is mission-specific, the data model is specific to the agency, or forcing a generic platform to fit would cost more than building properly. See custom software development for government.
Consolidate several applications into one when critical work is spread across separate systems that share data, users, and staff time. One platform gives the agency a single source of truth and ends duplicate entry.
Extend or rescue what you already run when the platform is sound and the application needs documentation, maintenance, or repair. We build, extend, and maintain Quickbase and other low-code applications for government clients. See Quickbase App Rescue.
Six phases, with the weight on what the old system knows
Every engagement runs on the same documented methodology. On a legacy replacement, each phase carries extra weight on preserving the data, the rules, and the decisions built into the old system.
Phase 1
Discovery & Requirements
We run working sessions with the people who use and depend on the system, including original developers where they’re available, audit the current environment, and inventory the data. You sign off on the requirements before any build begins.
Phase 2
Design & Architecture
We produce the system architecture, the data model, the integration design, and the security and access-control design. For systems with significant user interfaces, your staff review a clickable prototype before development begins.
Phase 3
Development & Integration
Working software arrives at a steady cadence. Every third-party integration sits behind its own component with a development stand-in, and data migration is prepared in parallel: extraction, transformation, and staging.
Phase 4
Testing & Validation
User acceptance testing with your own staff is the acceptance gate. Migrations are validated through a staged migration and parallel-run verification, confirming the new system matches the old one on real data.
Phase 5
Deployment & Training
The deployment runbook is rehearsed in staging first, then go-live happens in controlled steps with validation checkpoints. Staff are trained through a train-the-trainer program and receive the full documentation set.
Phase 6
Ongoing Support & Optimization
Ticket-based support with defined response times, quarterly system reviews, and ongoing enhancements, so the agency is never again dependent on one person to keep a critical system running.
See our government software delivery methodology for the full framework.
Data migration you can audit
Data migration is where most legacy replacements go wrong, so we treat it as its own discipline. Data is inventoried in discovery, mapped, cleansed, and staged during development, then validated through a parallel run before cutover, so the result can be reconciled against the source system.
We have migration experience with Microsoft Dynamics GP and Great Plains, older Sage versions, custom databases, flat files, and legacy government applications, including 300,000+ documents migrated under contract.
300,000+
documents migrated under contract
Delivered inside formal procurement
RFP and procurement fluency
We respond to formal solicitations and deliver against the contracts that follow, working through the channels and on the terms each solicitation defines.
Documentation and change control
Requirements specifications, status reports, change logs, and deliverable records accumulate as the work proceeds, so the people who inherit the system can run it.
Security designed in
Our government builds run on AWS with role-based access and audit-ready delivery, and data protection is designed in during architecture. See security and compliance for public-sector software.
Continuity
Watkyn has been operating since 2015, with a documented methodology and a team structured so no project depends on one person. We’re a strong fit for agencies that want a practical modernization partner rather than a large systems integrator.
Legacy replacement and consolidation in our government record
Colorado Office of the Alternate Defense Counsel
Consolidation of four legacy applications into a unified cloud platform; 300,000+ document migration; role-based access control; SFTP integration with the state CORE financial system; reporting and pipeline-based system integrations. AWS, PostgreSQL, React, Cognito.
Relevant to agencies replacing aging, single-developer legacy systems with documented, maintainable cloud infrastructure. Built with agency staff in working demos every week of development, so staff familiarity began well before go-live.
Southwest Utah Public Health Department
Quickbase permitting and compliance system for public-health regulatory operations, rebuilt to replace a partially working prior implementation, with corrected data relationships and record matching, regulatory letter and notice templates, and staff self-service for ongoing maintenance.
Relevant to regulatory and public-health agencies that need reliable permitting and compliance workflows and the ability to generate official communications without developer involvement.
American Samoa Medicaid State Agency
Multi-year Quickbase operational platform for the territory’s Medicaid program, built and maintained in direct collaboration with agency staff since October 2021.
Relevant to government agencies needing sustained, multi-year low-code development and a durable support relationship.
City of Philadelphia, Department of Commerce / PIDC
A department-wide platform for the Department of Commerce and the Philadelphia Industrial Development Corporation (PIDC) that began with emergency relief delivery and grew to run the department’s economic-development programs, 2020–2026. Read the Philadelphia case study.
Relevant to municipal programs that need to launch and run multiple funding programs quickly, with auditable review and a single source of truth across initiatives.
This work was performed for The City of Philadelphia and its Office of the Director of Commerce.
Scope, duration, and environment for each engagement are listed in our government past performance. We’re glad to provide references relevant to your sector and project, where permitted, on request.
What your agency receives
A typical engagement leaves you with a requirements specification, system architecture, data model and dictionary, migration and integration plans, a security and access-control design, test and UAT records, training materials, user and administrator guides, a go-live checklist, and a support plan, plus change logs and status reports throughout. The new system and its data are yours.
Questions agencies ask about legacy system replacement
Data is inventoried and assessed in discovery, staged and prepared during development, then validated through a staged migration and parallel-run verification, confirming the new system matches the source on real data before anyone relies on it. The deployment runbook is rehearsed in staging, and go-live happens in controlled steps with validation checkpoints.
We have migration experience with Microsoft Dynamics GP and Great Plains, older Sage versions, custom databases, flat files, and legacy government applications. The method is documented and repeatable.
Yes. It’s some of the work we know best. We work closely with the people who hold the institutional knowledge, including original developers where they’re available, map the full scope of what the old system does, migrate the data intact, and deliver a documented successor built to be maintainable.
Often, when the systems share data, users, or processes. One platform ends duplicate entry and gives the agency a single source of truth. For the Colorado Office of the Alternate Defense Counsel, we consolidated four legacy applications into a unified cloud platform. Discovery maps every source system and its data first, so the decision rests on what the systems actually do.
Yes. Responding to solicitations and delivering against the resulting contracts is core to how we work. Send us the solicitation and we’ll give you a straight read on fit before you invest time evaluating us.
Yes, where permitted and appropriate to the project type, after confirming the client’s availability and clearance to serve as a reference.
You do. Our custom builds run in your environment, under your control, with no per-user licensing lock-in.
It depends on scope, data migration, integrations, security requirements, and the level of ongoing support, so we don’t quote a replacement from a short form or a single call. We start by understanding the current system, the workflow, the data, and the risks, then define a scope and a delivery plan you can evaluate.
Tell us about the system you need to replace.
Send us the solicitation, or tell us about the system you need to modernize. We’ll give you a straight read on fit, the likely approach, and where the risks sit, working within whatever your procurement process allows.
Questions, or something specific you’re weighing? We’re happy to talk: 201-644-5251.
