Skip to main content
Boermans Digital
Main menu

Decision guideAutomation

Moving data between CRM and ERP: integration or RPA?

Sales updates a customer's address in the CRM. Finance still has the previous address in the ERP. Someone copies the change across, but which version should take precedence? That question needs an answer before the handover is automated.

Fictional example: transferring information between CRM and ERP. Check which integrations your systems support.

Let the transfer trial determine the route

A demonstration that creates one customer does not prove an integration is manageable. Also test what happens when confirmation is missing, data changes or input is rejected.

On a narrow screen, focus the table and use the arrow keys to scroll.

From observation to decision
Test caseWhat you want to establish
The same change is submitted again.Whether the same business change is performed again and how repetition is recognised.
The destination processed the change, but confirmation never reaches the source.How to establish the actual outcome before trying again.
A field is missing or has an invalid value.Whether rejection remains visible, who corrects it and how processing resumes.

Fictional example: transferring an approved customer

Sales approves customer K-104 in the CRM. The ERP owns payment terms. The trial transfers only the agreed customer fields and leaves existing payment terms unchanged. Use fictional records in an agreed test environment.

After processing, the connection fails before confirmation returns. A new attempt must not blindly create another customer. Investigate which unique reference and destination-status check the available interface supports. If the outcome cannot be established reliably, have a responsible person investigate it first. Test the same failure cases with RPA: controlling a screen does not remove this problem.

Record the outcome for each route

  • Link every test case to source and destination evidence, not only a green dashboard.
  • Record supported features, missing capabilities and required operational tasks.
  • Then select the route and decide who manages corrections and changes.

Record the event, systems and exceptions in the process canvas

Technical background: Microsoft: Idempotent Consumer (consulted 14 October 2026) explains handling repeated messages. The trial design is our own assessment; this source does not prove your CRM, ERP or robot is configured this way.

Key terms explained

An API is an agreed way for software to request or pass on data. An API integration lets systems communicate directly; RPA operates existing screens. The right route depends on what the systems support and how failures can be recovered.

Start with one change, not two entire systems

Choose a specific event: an approved customer is created, a billing address changes or an order moves to a new status. Define which fields should move, in which direction and within what time window. Overnight processing may suit one record, while another process needs up-to-date information sooner.

Assign an authoritative source and an owner for each field. Sales might own contact details while finance controls payment terms. Saying that the systems should synchronise is not enough. Agree what happens if someone changes the same field in the other system while a transfer is in progress.

Compare the conditions behind each route

Check the options in this order. The first available option is not automatically the right one: it also needs to support the required data, checks and recovery.

  1. Existing feature: can your current software already perform the handover?
  2. API integration: can both systems exchange the required data with appropriate permissions?
  3. Import and export: does scheduled processing meet your need for up-to-date information?
  4. RPA: if screen-based actions remain necessary, who manages sign-in, screen changes and failures?

On a narrow screen, scroll the table sideways. With a keyboard, focus the table and use the arrow keys.

This is not a ranking. Suitability depends on the applications and the process.
RouteCheck firstWatch for
Existing integrationDoes it support the required fields, direction and events?An available connector may not cover every exception.
API or workflow integrationAre access rights, limits, error responses and support clear?The interface still needs mapping, maintenance and recovery.
Import and exportAre the format, timing, versioning and processing confirmation adequate?Receiving a file does not mean its records were accepted.
Screen-based RPAIs the action permitted and is the interface predictable?Screen changes, sessions and additional sign-in steps can require maintenance.

A combination may be appropriate: a supported export for the records and a workflow for approval, for example. Do not choose screen automation simply because a demonstration is quick to build. Establish who will retest the process after application changes.

A customer identifier is not universal

Map the meaning, format and required values of each field. A CRM organisation identifier may need to be matched to an ERP customer account. Decide how that mapping is maintained and who resolves missing or conflicting values. A company name alone is not a generally reliable key.

Test a new customer, an existing customer, an amendment and a deliberately blocked account. Include unusual characters, long names and blank optional fields. A technically successful transfer can still leave the receiving system with the wrong information.

What if no confirmation comes back?

The source sends a change but receives no response. That does not prove that the change failed. Check the receiving system before sending the same instruction again. Where supported, a stable identifier for the operation helps prevent duplicate processing.

Make differences between source and destination visible and assign someone to resolve them. An invalid address may require correction; a temporary connection problem may justify a limited retry. Define those paths in advance, including the point at which a person takes over.

Discuss maintenance before selecting a solution

  • Who owns accounts, permissions and connection credentials?
  • How are errors reported without copying unnecessary customer data into alerts?
  • Who checks changes to fields, screens and interfaces?
  • How are totals and rejected records reconciled?
  • Can an operator stop the process and recover it in a controlled way?

Ask the application suppliers which interfaces and automation methods they support. Being able to access a button or endpoint does not automatically mean unattended use is permitted. Include licensing, maintenance effort and reliance on individual employees in the decision.

Bring a concrete handover to the discussion

Prepare an anonymised example of the change, the applications involved and the current checks. Focus on where the handover breaks down. That gives you a basis for assessing whether an existing feature is sufficient or an additional integration is justified. Tool selection follows from that understanding.

Related guide: RPA, workflow or AI?

Compare the conditions for a managed integration with Harmonizer. If a direct integration is not possible, first discuss which approach fits the systems and process.

Where does your data handover break down?

Describe the information that needs to move between your systems. We can explore the question together, even if the right approach is not yet clear.

Discuss your data flow

Explore your process with the Automation Scan

Boermans Digital / privacy

Your cookie preferences

You decide whether Google Analytics may load. The website, scans and calculator also work without Analytics.

Completed fields, scan answers and calculator results are not sent to Analytics.

Which data and retention periods?

We remember your choice on this device for up to 180 days, including a refusal. The _ga and _ga_* Analytics cookies are configured for up to 180 days. Retention at Google is configured separately in the Analytics account.

Storage for website functionsFunctional

The website remembers your privacy choice. Only when you choose to switch language can scans, the guide and calculator temporarily carry answers within the same tab. Contact details are not stored in that transfer.

Contact form protectionAt request review

Google reCAPTCHA loads when you open the review of your completed request. Google then processes technical data and may use security cookies. This is separate from your Analytics choice. Contact by email remains available.

Analytics is off.