System integration forthe workflows your business runs on.
We connect the systems a workflow touches, so your team enters data once and each system holds the current version. That includes ERP, CRM, Teams and OneDrive, tender and project platforms, and custom apps.
Salesforce partner since 2018The systems exist. Your data has to move between them.
A new CRM, portal or AI agent is only as good as the data it can reach. Prices sit in the ERP, project leads on a tender platform, documents in SharePoint, and each team sees only its own part of the process.
Your team types data twice
Someone enters an order in one system and retypes it in the next. Each copy can hold an error, and each system shows a different version.
The record has no owner
Customer, price and stock data exist in several places. Without a decision on which system is the master, the copies disagree.
Old systems stay
Legacy systems and file formats stay in use for years, and the new tool has to work with them.
We start with the data and the process, then connect the systems around them.
Every system your workflow touches
These are the systems we have worked with. If yours is not on the list, ask us.
ERP
R/3- S/4HANA
- Navision
Accounts, orders, prices, stock and master data move between your ERP and the systems your sales and service teams use.
CRM
Customers, projects and quotes in Salesforce stay in step with your ERP and the other systems around it.
Collaboration and documents
Teams
SharePoint
OneDrive
d.3- Lotus Notes
We link documents, conversations and older archives to the customer record, so people find them where they work.
Tender and project data
Project leads, tender documents and bills of quantities reach your CRM or app in the formats the industry uses.
Product planning
Product configurations and planning data move between pCon and your CRM, ERP or app, so nobody retypes them.
Reporting
Power BI
Data from your ERP, CRM and other systems feeds Power BI, so reports use the same current figures.
Middleware
- PI/PO/XI
- BizTalk
Where several systems exchange data, a middleware layer carries it, with central monitoring and one place to change a mapping.
Custom apps
Your own applications and standalone apps we build
Interfaces to in-house tools and standalone applications. We document and test them, so you can take them over.
Decide who owns the data, then build the connection
Map the data
We list which systems hold which records, who changes them and where they go next.
Name the master
For each type of data, such as accounts, prices or stock, one system is the system of record. The others read from it or send updates to it.
Choose the connection
A direct API, middleware such as MuleSoft, SAP PI/PO/XI or BizTalk, or a file exchange. We pick what fits your IT landscape.
Plan for failure
Interfaces fail: a system goes down, or a system rejects a record. We build in logging, retries and alerts, so someone sees it before a user does.
Document and hand over
We document and test each interface, so your IT team can run it and change it.
Integration that customers describe in their own words
Messer · Industrial gases · Messer Schweiz AG
“IBS Technology plays a crucial role as our design and implementation partner in our CRM project. Accompanying us during the pre- and post-implementation phases, they have successfully tackled and overcome the challenges of integration with other IT systems.”
RECKLI · Architectural concrete · Recklinghausen
“Thanks to the good interfaces and the support from the Salesforce partner IBS Technology, the integration ran smoothly.”
AI agents only work on connected systems
An agent that reads a quote request is only useful if it can look up the price and write the order. Integration gives AI access to your real data. Our security page describes how we protect that data.
Connecting business systems
Should we use middleware or a direct API connection?
A direct connection suits two systems with stable interfaces and modest data volumes. Middleware, such as MuleSoft, SAP PI/PO/XI or BizTalk, pays off when several systems exchange data and you want central monitoring. The right choice depends on how many systems are involved and who in your IT runs the connection. Sometimes the direct connection is enough, and we say so.
Which system should be the master for customer and price data?
Usually the ERP owns prices, stock and billing data, and the CRM owns contacts, projects and sales activity. Each type of data has one owner, and the other systems read from it or send changes to it. Agree on this before building anything, because unclear ownership causes most sync conflicts.
Can you connect an old or custom system that has no API?
Often, yes. The options include a file exchange, a database connection or a small service placed in front of the old system. Each one has trade-offs in reliability and upkeep, and we lay them out before you commit. For some systems, replacing a part is the better answer, and we say so.
How long does a system integration take?
It depends on how many systems are involved and how clean the data is. Cleaning data and agreeing ownership can take as long as writing the interface. The blueprint says what gets built, where and in what order, before you commit to a build.
What do we need to provide for an integration project?
Access to the people who run the process, a few real records as examples, and one contact from IT who can open the systems involved. We handle the rest of the analysis. A test system helps, and without one we agree a safe way to test first.
What happens to the integration after go-live?
Each interface comes with documentation, automated tests and alerts that show when a transfer fails. Your team can run it and, with training, change it with AI. For new integrations or anything that needs an architect, we are available on request.
Tell us which systems need to talk to each other
Describe your systems and your process. Our team will tell you how we would connect them.