ERP & accounting
Orders, items, customers, invoices, entries. Depending on the ERP: API, database, or scheduled imports and exports.
Systems integration
Your software works together.
Most re-keying comes from software that does not talk to each other. We connect your ERP, CRM, accounting, e-mail and databases, with exchanges that are controlled, traceable and reversible.
- Interfaces
- REST or SOAP APIs, SQL, files, e-mail, webhooks.
- Systems
- ERP, CRM, accounting, DMS, business applications, existing databases.
- Approach
- Read-only first, test environment, gradual go-live.
What we connect
The tools you already use.
We start from your current environment. Changing software is almost never a prerequisite.
CRM & sales
Contacts, opportunities, quotes and activities, synchronised with e-mail and your website forms.
Shared inboxes, attachments and replies. Reading via IMAP or API, sending via SMTP or API, with traceability.
Databases
SQL Server, PostgreSQL, MySQL, SQLite or Access. Controlled reads and writes, verified queries.
Files & data exchange
Excel, CSV, XML, PDF, shared folders, SFTP. Scheduled imports and exports, with format checks.
Business applications & SaaS
Industry-specific software and online platforms. Existing connectors when they are reliable, dedicated development otherwise.
Legacy systems
Legacy systems are not an obstacle.
An Access database, an Excel workbook with macros or software without an API often remain at the heart of an SME. We can read them, connect them to newer tools or prepare their migration where it makes sense.
- Reading Access databases and Excel workbooks without modifying the original.
- Extracting the structure, queries and VBA code to document the existing system.
- Gradual synchronisation with a newer tool, without interrupting operations.
- Data migration with row-by-row checks between source and target.
Approach
How we integrate a system.
- 01
Interface inventory
We check what each piece of software actually allows: API, database access, exports, limits and permissions.
- 02
Data mapping
Fields, formats, identifiers and transformation rules are documented before development.
- 03
Test environment
Exchanges are developed and tested on a copy or in a separate environment, read-only at first.
- 04
Gradual go-live
Running in parallel with the existing system, reconciling results, then switching over.
- 05
Monitoring
Every synchronisation is logged. A discrepancy or error triggers an alert.
Technical safeguards
A data exchange must be able to fail without causing damage.
Network outage, third-party system unavailable, message received twice: these situations happen. They are anticipated from the design stage.
- Idempotency
- Each exchange carries a unique identifier: a retry never creates a duplicate.
- Retry
- An unavailable system is retried with an increasing delay, then the incident is reported.
- Reconciliation
- Synchronised data is periodically compared between systems.
- Permissions
- Dedicated technical accounts, limited to the data and actions required.
- Secrets
- Credentials stored on the server side, never in a browser or in the source code.
- Traceability
- A log of every exchange: origin, destination, summary of the content, result.
Frequently asked questions
Integration, without unpleasant surprises.
Our software has no API. Is it still possible?
Often. An accessible database, scheduled exports or exchange files may be enough. We identify the most reliable option during the analysis, and we tell you clearly if none of them is reliable.
Do we need to give you administrator access?
No. We ask for dedicated technical accounts, limited to the data and actions required, which you can revoke at any time.
Do you use platforms such as n8n?
When it is the right building block, yes: n8n can be self-hosted and remains readable. For critical exchanges, we prefer dedicated code that is tested and versioned.
What happens if a piece of software is upgraded?
Integrations are documented and monitored. An error caused by a change is detected by monitoring; the adaptation is covered by the operations contract or quoted separately.
Integration
Two applications that don’t talk to each other?
Tell us which ones and what is re-keyed today. We check the available interfaces before proposing anything.