Connecting an old in-house system to your ERP or Microsoft 365

To connect an old in-house system to a new ERP, Dynamics 365 or Microsoft 365 when its developers have gone, someone first reads its code and database, then gives it a supported way in: an API, a middle layer or a scheduled exchange. This page is for IT managers at medium and large organisations whose new platform has to work with a system nobody fully understands any more. CodeFirst, a UK software company, builds that connection on the side of your own system; the ERP itself stays with its supplier or partner.

By Graham Church, founder and managing director. Updated 14 October 2026.

The short answer

Start with the old system, not the ERP. Dynamics 365, other modern ERPs and Microsoft 365 publish documented interfaces, so the new side is rarely the problem. The work is in understanding a system whose builders have gone, deciding how data should flow, and adding a way in that does not break it.

Why old systems are hard to connect

Most in-house systems were built to stand alone. Connecting them is hard for a few common reasons:

  • No API. The system was never designed to be called by anything else. Its only interface is its own screens.
  • Direct database access. Other tools already read or write its tables, so nobody is sure what depends on what.
  • File drops. Data leaves as a nightly CSV export to a shared folder, picked up by a script on someone’s PC.
  • Nobody knows the data model. Column names are cryptic, some fields mean something different from their name, and business rules live in the code rather than the database.
  • No test copy. Without a safe copy of the system and its data, every experiment is made against live data.

None of this rules out an integration. It means the first job is to find out how the system works.

What to check first

Who owns the data. Each kind of record needs one master. If customers can be edited in the old system and in the ERP, an integration only moves the disagreement around faster. Decide which system holds customers, products, prices, jobs and invoices, and which receive copies.

What the old system already does. Look for exports, imports, scheduled jobs and other programs that read its database. They show what already depends on it, and sometimes give a ready-made route out.

What the ERP and its licence allow. Check which interfaces your edition offers, whether API access costs extra, and who at the supplier or partner will agree the interface with you.

How failures will be handled. Decide now who is told when a record cannot be transferred, how quickly, and how it is put right. An integration with no error handling or monitoring drops records quietly, and the first sign is a figure that does not match at month end.

Your options

Add an API to the old system. Where you have the source code, a small interface can be added that reads and writes data through the system’s own rules. This is the most robust route, and it needs someone who can safely change the old code.

Put a middle layer between them. A separate service, for example on Azure, takes data from one side, translates it and delivers it to the other. It queues records, retries failures and keeps a log. Each system only needs one connection, to the middle layer.

Exchange data on a schedule. Files or database staging tables, processed every few minutes or overnight. Simpler, and often enough when nobody needs the data instantly.

Replace the re-keying first. If staff copy records by hand today, automating that one hand-off is usually the quickest gain. Where the data arrives as emails or PDFs, AI can read it in for a person to confirm.

Retire the old system. If the ERP covers what it does, a one-off data migration may cost less than a link you will have to maintain.

What we do

We read the old system’s code and database, the same first step as taking a system over, and write down how its data is structured and where it already sends and receives records. We then agree the interface with you and, where needed, with your ERP partner. We build the integration with logging, retries and alerts, run it beside the manual process until the results agree, and hand over the code and documentation.

Our system integration package connects two systems at a fixed price. If nobody can support the integration afterwards, it can sit under a maintenance arrangement along with the old system itself.

Recommended next step

System integration

Start with the hand-off that costs most: this package connects two systems at a fixed price, with failures reported and every transfer logged, and checks both ends before quoting.

Ways an old system can be connected

An API added to the old system
Where the source code is available, a small, documented interface is added so other systems can read and send data without touching its database.
A middle layer
A separate service, often on Azure, sits between the old system and the ERP. It translates the data, queues it, retries failures and keeps a log, so neither system needs to know about the other.
Database-level exchange
Records are read from the old database, or written to staging tables it already processes. Works without the source code, but must respect the system's own rules.
Scheduled file exchange
The old system already writes or reads files, often CSV. The integration picks them up and passes them on. Old-fashioned, and sometimes the only safe route.
The ERP's own interfaces
Dynamics 365 and Microsoft 365 publish documented APIs, and Power Automate covers simple flows. The hard part is almost always the old system, not the Microsoft side.
AI reading documents
Where data arrives as PDFs or emails rather than from a system, AI can read it into the ERP, with a person checking anything uncertain.

How we go about it

  1. Read the old system

    We read its code and database, and find the files, reports and scheduled jobs it already uses to exchange data. The result is a written description of where each record lives.

  2. Map the hand-offs

    We list each place where data moves between the old system and the ERP or Microsoft 365, by hand or otherwise, and agree which system is the master for each kind of record.

  3. Choose the interface

    An API, a middle layer, a database exchange or files, chosen from what the old system can safely support and what the ERP's licence allows.

  4. Build it with failure in mind

    The integration logs every record, retries what can be retried, sets aside what it cannot process and alerts a named person.

  5. Run it alongside the manual process

    For an agreed period both run and the results are compared. Then the manual step is dropped.

  6. Hand over or support it

    You get the code and documentation. We can support the integration afterwards, or your own team can.

A good fit when

  • A new ERP, Dynamics 365 or Microsoft 365 is going in, and an older in-house system has to keep working beside it.
  • The people who built the old system have left, and nobody knows its data model.
  • Staff re-key orders, customers, jobs or invoices from the old system into the new one.
  • An existing link between the systems fails without warning, and nobody notices for days.

Probably not for you if

  • You need Dynamics 365 or another packaged ERP configured, customised or supported. That is work for the product's supplier or a Microsoft partner; we work alongside them on the interface.
  • A ready-made connector already does what you need. Switch it on; you do not need us.
  • The old system is due to be switched off within months. Moving its data once may make more sense than building a lasting link.

Questions we are asked

Can an old system be integrated when the original developers have gone?

Usually, yes. The code and database still describe how the system works, even when nobody remembers. We read them, write down the data model and the existing feeds, and design the integration from that. Having the source code makes more options possible; without it, the database and any file exchanges are the way in.

Do you implement or configure Dynamics 365?

No. The ERP is set up and supported by its supplier or a Microsoft partner. We work on the other side of the connection: your in-house system and the integration between the two. We deal with the partner's team on the interface, so the two halves fit.

Is it safe to write straight into the old system's database?

Only with care. Old systems often enforce rules in their code rather than in the database, so a record written directly can skip a check or a calculation. We find out what the code does when it saves a record, and either repeat those rules or add an interface that uses the system's own code.

Where should the integration run?

Usually as a small service of its own, on Azure or on a server you already have, not inside either system. That keeps the old system unchanged where possible and gives one place to look when something goes wrong.

What happens when an integration fails?

That depends on how it was built. A careless one fails silently, and you find out when the figures do not match. A careful one records every message, retries, and tells someone when a record needs attention. We build the second kind.

Should we replace the old system instead?

Sometimes. If the new ERP already does its job, moving the data across and retiring the old system is often cheaper over time. If the old system does something specific to your organisation that the ERP does not, connecting the two is usually quicker and lower risk.

Tell us about your system

Say what it does, what it is built on and what is worrying you. We will reply with what we would look at first and whether we are the right people to help.

Discuss an integration 0800 433 7990 Monday to Friday, 9am to 5pm. A first 20-minute call is free, and we reply to every enquiry within one working day. What happens after you get in touch