Cartagena Link
Configuration-based integration between Dynamics 365 and ERP
Many ERP/CRM integrations start as small custom scripts and end up as business-critical infrastructure no one dares touch. Cartagena Link replaces fragile point-to-point code with a tested, configuration-based platform, with logging, error handling and control over the data flow.
Talk to an expertWhat Cartagena Link does for you
You choose what to sync
Customers, contacts, products and orders flow between Dynamics 365 and your ERP. You choose what syncs, in which direction, and how conflicts are handled.
Logging, monitoring and error handling
Transaction logging, error alerts, retry handling and audit trail for every sync operation. When something fails, you see what happened and what needs attention.
Configuration, not custom code
Define mapping, sync rules and data flow through a tested cloud platform. When your ERP setup changes, you adjust the configuration rather than rewrite code.
Our team explains the concept
Configuration-based integration
See how ERP and CRM data flows without custom code
CRM + ERP in 3 steps
Connect your systems with configuration, not coding
Supported ERP Systems
Don't see your ERP? We can build custom connectors for most systems.
How it works
Define
Together we map data flows, direction, master data ownership and data quality requirements.
Configure
We configure the integration using our platform: mapping, sync rules and error handling without custom development.
Test
We validate the data flow in a test environment before going live.
Go live
Standard configurations typically go live within days. Complex setups with custom mapping or data migration take longer.
Frequently asked questions about Cartagena Link
What is the difference between Cartagena Link and a point-to-point integration?
A point-to-point integration is written for one particular setup and has to be rewritten when the ERP setup changes. Cartagena Link is configuration-based: mapping, synchronisation rules, direction and conflict handling are defined in the platform rather than in code. When the ERP changes, you adjust the configuration. Logging, error alerts and an audit trail come with it, rather than having to be built each time.
Which ERP systems are supported?
Ready-made connectors exist for Visma, Dynamics 365, Xledger and Tripletex. For other systems we build custom connectors, provided the ERP has an API or another defined interface. What drives the cost is rarely which ERP it is, but how much of the data model has been customised.
How long does it take to go live?
Standard configurations typically go live within days. Complex setups with custom mapping or data migration take longer. The work moves through four steps: define the data flow and master data ownership, configure mapping and rules, validate in a test environment, and go to production.
Who should own customer and product data when CRM and ERP are connected?
That is the most important clarification, and it is organisational rather than technical. One system has to be authoritative for each class of data, otherwise conflicts arise that no integration can resolve. In practice ERP usually owns product, price and invoice, while CRM owns the dialogue and the sales process. The customer record is the one that most often requires an explicit decision.