System integration and data
A new system rarely replaces all the previous ones. Integration is about making the systems that stay in use exchange data automatically, instead of through a file export and a manual import.
Exchange, reference data, migration
The volume of integrations is the main reason a project estimate changes after the survey.
Exchange between systems
Accounting, HR, banking clients, industry registries. Through APIs or scheduled exports, depending on what the system is actually capable of.
Shared reference data
Counterparties, item catalogues, departments, cost lines. As long as one counterparty exists in three systems under three names, the data cannot be consolidated.
Data migration
Reference data, balances, document archive. Planned as its own block with its own deadlines — this is where projects slip most often.
Reconciliation after transfer
Control totals, balance comparison, sample checks of documents. Migration without reconciliation is a transfer of errors into a new system.
Single sign-on
Login through the corporate directory, so accounts are not created separately in every system and are disabled at once when someone leaves.
Consolidated reporting
When data from several layers is needed in one report — without a monthly manual consolidation in spreadsheets.
Where integration becomes an endless project
We do integration within an implementation and against a fixed list — otherwise it has no natural end.
"Integrate everything with everything"
The list of exchanges is fixed during the survey. Every additional direction is a separate estimate, not "a small thing, add it while you are at it".
Dirty reference data
Duplicate counterparties and inconsistent catalogues stop an exchange faster than any technical limitation. Cleaning it up is a separate piece of client-side work.
No system of record
If it is not agreed where the "truth" lives for each reference book, two layers will start overwriting each other.
Migration as an afterthought
It is placed last in the plan and underestimated several times over. We make migration a separate stage with its own date.
No access to the old system
Sometimes an export is only possible through the previous contractor. That surfaces during the survey, not a week before go-live.
Exchange without monitoring
If nobody sees that the nightly export failed, it is discovered a month later as a discrepancy in reporting.
Articles on this topic
No articles in this category yet.
The "Data and integrations" stage in the overall order of work is on the How We Work page. Platform exchange mechanisms are on the Solutions page.