ERP integration

We work with SAP S/4HANA and SAP Business One, Oracle NetSuite, Oracle Fusion Cloud ERP, Microsoft Dynamics 365 Finance and Supply Chain Management, Dynamics 365 Business Central, Odoo, Sage Intacct and Sage X3, as well as custom and older systems. For each we use the interfaces the vendor supports, so upgrades do not break the integration. Naming a product does not mean a partnership with its vendor.

Not always. A few stable flows between two systems can be direct API calls. Once several systems exchange data, or you need mapping, queues and monitoring in one place, middleware such as MuleSoft, Boomi or Azure Logic Apps usually pays for itself. If you already own one, we build on it. We set out the trade-offs, including licence costs, before you decide.

It rarely is, and it is the most common reason integrations fail. Early in the work we profile the customer, item, price and account data each flow depends on, and show you the duplicates, gaps and conflicts we find. We agree which system owns each record and add validation so bad data is stopped at the edge rather than copied everywhere.

It depends on the number of systems and flows, how well each system’s interfaces are documented, the state of your master data, and how quickly test environments and access are ready. Partner approvals, such as a bank or a marketplace, can set the pace too. After the assessment we give you a plan flow by flow, so the most valuable connection goes live first.

The number of interfaces, the complexity of the mapping and business rules, the volumes and timing each flow needs, and whether middleware licences are involved. Data clean-up and testing with partners add effort. We estimate per interface after the assessment, so you can see the cost of each flow and decide the order.

We build on the interfaces the vendor publishes and supports, not on database tables or screens, so most upgrades leave the integration untouched. Before an upgrade we review the vendor’s release notes against each interface, run the test suite on the upgraded test system, and fix anything that changed before production moves.

Each integration uses its own technical account with only the permissions its flows need, never a person’s login. Credentials live in your secrets store, not in code. Our engineers work in test systems with masked or sample data where possible, and their access is named, logged and removed when they leave the project.

Intellectual property in the work we build for you is yours from the first commit — no assignment step at the end. That covers the custom code, documentation and other deliverables made for you. Anything we bring that existed before, such as internal tools or libraries, stays ours, and you receive a licence to use it in your systems. Open-source components keep their own licences, and we list them for you.