Talk to us

Take it on

COBOL modernisation: we fix it, then we get you off it

If business-critical work is running on COBOL, you already know the problem. It works. The risk is that it won't always, and fewer people can maintain it every year. We assess, document and migrate COBOL systems properly, without losing the logic built up over decades.

You'll be talking to one of us, not a salesperson.

We have a COBOL developer. His name's Kevin.

That's not a common thing to find in a UK software company. Kevin is part of the team here, which means we read the code ourselves, document the business logic in it, and make sure none of that's lost when we rebuild it in modern PHP, Python or Laravel.

We're not recommending COBOL. We're rescuing you from it.

COBOL isn't broken

In many organisations it's the most reliable thing they run. It handles batch processing, financial calculations, payroll, billing and logistics with a stability many modern systems can't match, and it's been doing that for 20, 30 or 40 years.

The problem isn't performance. It's risk and dependency.

The risks that build up

  • Fewer people

    The number of developers who can read COBOL falls every year, mainly through retirement.

  • Harder to connect

    Modern infrastructure and cloud platforms don't speak COBOL, so integration gets more awkward and expensive.

  • Knowledge walks out

    Business logic built up over decades sits in the code. When its authors retire, the understanding goes too.

  • Audit expectations

    Regulators increasingly assume modern, auditable systems, and COBOL can struggle to show the trails they expect.

  • Failure cost

    A critical failure in a system nobody fully understands costs far more than a controlled migration.

There's nothing wrong with old code that still works. The real risk is when only one person left understands it. We modernise these systems carefully, in stages, so you're never betting the business on a big-bang switchover.
Rob Sherwood, co-founder

Why COBOL migrations are different

  • Undocumented logic

    Edge cases and exceptions added over the years are invisible until something breaks. Getting them out takes someone who knows the language.

  • Old data structures

    Copybooks and fixed-format files are nothing like relational databases or JSON. You have to understand both ends.

  • Batch complexity

    Sequencing, dependencies and error handling have to be replicated without changing the business outcome.

  • Hidden dependencies

    Other systems were built around assumptions about COBOL's output. Change one thing and others feel it.

  • No test suite

    Usually the only proof it works is that it's been running for years, so you need a test strategy before you touch it.

  • The knowledge gap

    The people running it know what it does, not why. Closing that gap means reading the code, not asking around.

How we handle a migration

  • 1. Audit and logic extraction

    Kevin reads and documents the system: every rule, data transformation and exception path, in language both technical and business people can follow. This is the most important phase.

  • 2. Dependency mapping

    Every system and process depending on the output, including undocumented assumptions about format and timing.

  • 3. Target design

    We design around what the system needs to do, not what's easiest to build. Batch pipelines, APIs, web screens and reporting each suit different approaches.

  • 4. Parallel build and validation

    The new system runs alongside the old one, and outputs are compared on identical inputs until they match, edge cases included.

  • 5. Data migration

    Historical data is transformed and moved, then its integrity is checked before cutover.

  • 6. Controlled cutover

    The switch happens at a planned point with a rollback plan. We monitor closely afterwards, and the old system stays available as a fallback until the new one has proved itself.

The systems we see

The sector matters less than understanding the logic.

  • Financial processing

    Batch payments, ledgers, tax calculation and reconciliation, often overnight jobs feeding morning reports.

  • Payroll and HR

    Complex tax and deduction logic refined over many years and barely documented outside the code.

  • Logistics and inventory

    Order processing, stock and despatch, often tied into other old systems.

  • Insurance and administration

    Policy, claims and actuarial logic built up over decades.

  • Any critical batch pipeline

    If an overnight process feeds your operation the next morning and it runs on COBOL, we can migrate it.

What we move it to

The goal is more than replacing COBOL. It's something that will serve you for years without needing specialist knowledge, which means well-understood technology with plenty of developers.

  • PHP

    Web-facing applications, admin screens and anything needing a browser.

  • Python

    Batch pipelines, data transformation and heavy computation.

  • Laravel

    Complex application logic, API layers and systems connecting to several others.

  • MySQL and MariaDB

    Relational storage replacing flat files and VSAM datasets.

  • REST APIs

    Clean integration layers for everything downstream.

Should you migrate at all?

The first step is a conversation about what the system does, how critical it is and what a migration would involve. You'll get an honest view, including whether a different approach makes more sense.

We're generally against replacing things for the sake of it. AI helps too: it can explain unfamiliar code and speed up the documentation, and Kevin checks what it says. And once you're on the new system, we look after it.

Questions we get asked

  • Can you maintain our COBOL system for now?

    Yes, that's the first half of "we fix it, then we get you off it".

  • Do we have to do it all at once?

    No. We work in stages, so you're never betting the business on one big switchover.

  • What do you move it to?

    Usually modern PHP, Python or Laravel, depending on what the system needs.

  • What if nobody has documented it?

    That's normal. Producing the documentation is the first phase.

Photos of Rob and Jason, who run Dev Partners

Hello, you get us

Rob on the left, Jase on the right. No sales team and no account managers. One of us is on every job, from the first chat to long after it goes live, and the people writing your code sit in the same small team.

Meet everyone

Tell us what you've got

It goes straight to Rob and Jase. You'll hear back from one of us, usually the same day, and we'll tell you honestly whether we're the right people.

Just want it checked? Code audit, £250 + VAT