Understand the whole process before you connect anything.
An integration discovery and architecture review maps your systems, data flows and business rules, so the integrations you build next are reliable, supportable and ready for what comes after.
Most integration problems start before the first line of code.
An integration that only moves values from one place to another can quietly drop the rules, sequencing and confirmations that make the process correct.
We start with how your business actually works: which systems need the same information, where people re-key or export data today, and what has to happen for a transaction to be genuinely complete. Only then do we look at interfaces, platforms and tools.
The result is a clear picture of what to build, in what order, and how it will be supported once it's live, whether that's one integration or a connected estate.
What you get
- A map of your systems, interfaces and current data flows.
- The business rules, validation and sequencing each process depends on.
- Where re-keying, delays and hidden failures are costing you time.
- A recommended integration architecture and a prioritised roadmap.
- What monitoring, alerts and support tools you'll need once integrations are live.
Discovery questions that shape a good design.
These are the conversations that separate a simple data transfer from a complete, supportable business process.
Which systems need the same data, and how does it move today?
We map every system involved in the process and how information currently travels between them: APIs, files, exports, emails or people.
Where do people re-key, export spreadsheets or upload files by hand?
Manual steps show where integration will save the most time and remove the most risk of error.
Which delays are caused by one system waiting for another?
We look for processes that only become accurate after an overnight batch or a manual intervention.
When an interface fails today, how quickly can you find the record and the reason?
Supportability is part of the design: what evidence, alerts and tools will your team need?
Does the target need master data first? Does anything need writing back?
Many processes need suppliers, customers or items in place before transactions can flow, and need identifiers, statuses or payments returned to the source afterwards.
Are there record locks, approvals or sequencing rules?
These are what make a process more than a simple data transfer, and they need to be preserved.
Live access, scheduled batches, offline use, or a combination?
Not every process needs to be instant. Some are better scheduled or queued. We help you choose the right pattern for each flow.
Could the same layer support a future portal, app, BI feed or new service?
Designing for reuse now means your next project builds on a foundation rather than adding another point-to-point link.
The lifecycle we design for.
Discovery makes sure every stage is understood and accounted for before development begins.
Connect
Securely connect using the interface each platform supports: APIs, database, files, messages or specialist ERP services.
Capture
Identify the relevant records or changes without repeatedly extracting everything.
Validate
Check identifiers, required values, relationships, dates, statuses and business constraints before sending.
Transform
Convert source structures and terminology into the target system's business contract.
Submit
Send the request with the authentication, sequencing and message format the target requires.
Confirm
Interpret the response and decide whether the business transaction genuinely completed.
Write back
Where useful, return the identifier, status, payment or job number to the originating system.
Recover
Retry safely, hold failed work for intervention and protect source checkpoints so nothing is lost.
Monitor
Retain evidence, raise notifications and give support teams what they need to diagnose issues quickly.
Designed around your process, not one vendor.
We have particularly deep experience with UniData and UniVerse ERP environments such as Avante and InfoFlo, and we work with a wide range of other technologies where the source and target provide a suitable interface.
- ERP and business platforms, SQL-backed systems and legacy applications.
- Cloud and specialist applications with REST/JSON APIs and OAuth-secured access.
- SQL Server and other data-platform targets.
- JSON, XML, CSV and flat-file formats.
- Web and mobile channels, including OneGateway APIs and OneApp applications.
We worked very closely with Web Control on a Salesforce to Infoflo ERP project. The scope for the project was to be able to convert quotes in our Salesforce CPQ system into live orders within our Infoflo ERP, with the least amount of touch points from our Customer Service Team.
James and Jamie at Web Control were pivotal in not only the development, but also in the scope and design side of the project.
What really impressed us here at Nortek was the after service we received, on the most part dealing with bug fixes within a few hours. The program Jamie built for us has now been coined as the ‘Program of Dreams’.
Related pages.
Integration Support, Monitoring & Optimisation
Keep integrations visible, recoverable and improving.
Find out more NetSuiteIntegration Architecture & Options
Direct NetSuite integration or Patchworks iPaaS: choosing the right fit.
Find out more Legacy ERP SupportERP Consultancy & Process Improvement
Improve how your ERP supports the way you work today.
Find out moreModernise Without Replacing Your ERP
Extend, connect and automate around the system you already trust.
Find out moreThis site is in development and this page will be updated shortly.
Talk to us about your operations
Tell us how your business works today and where you want it to go. We'll listen first, then show you what could help.