Integration · written at the studio, London
API and legacy system integration
Wizards of Web Ltd · Saunders Ness Road · 23 October 2026
Wizards of Web Ltd connects existing software and updates legacy code for UK businesses. If you already have a website, a CRM, an accounts package or an old PHP application, we start with an integration plan. Then we connect the new feature with an API, or we change the old code so the new feature can live beside it.
API integration
This is the right path when both systems are staying. We map the records that have to move, how often, and what happens when one side rejects a record. The connection is logged so a failed sync is visible instead of silent.
Typical links are between a website and a CRM, a shop and a stock system, or an internal tool and a payment or email provider.
Legacy code
Some systems have no API. In that case we read the code that is live, name the part that has to change, and update that part. We do not propose a full rewrite when a smaller change will do.
If the old system is too brittle to extend, we will say that, and we will describe a replacement of one function rather than the whole company in one go.
A plan before the build
The first deliverable is the plan: what talks to what, what we will not touch, and how we will know the connection worked. You can stop after the plan if the build should wait.
Questions we get asked
What is API integration?
It is making two systems exchange records, such as a website creating a customer in a CRM, without staff typing the same details twice.
Can you update legacy code instead of replacing it?
Yes. We change the part that blocks the new feature and leave the rest of the system in place.
We already have a website. Can you use it?
Yes. We can keep the parts that work and add the new service beside them, or replace only the pages that are holding the business back.
Do you need access to the existing system?
We need a staging copy or a repository, and a test account for any third-party API. We do not experiment on the live system first.