Business Central CRM integration that ends the two-customer-list problem

What Business Central CRM integration achieves

A CRM tracks leads, opportunities and conversations. An ERP tracks orders, stock and money. They overlap on the customer. Without a connection, each one holds its own version of the name, address, contacts and terms. Sooner or later, an invoice goes to the wrong address.

Integration decides which system owns each piece of information. It then copies that piece to the other system. Sales sees credit limits, open orders and payment history. Finance sees which deals are about to close. Nobody keeps a spreadsheet to translate between the two lists, and each team keeps the tool it prefers.

Which route a Business Central CRM integration takes

Business Central has its own relationship management features: contacts, interactions, segments and opportunities. For a small sales team, that may be all the CRM you need. In that case you need no integration at all. We always check this first. It adds no extra product and keeps everything in a single application.

For Dynamics 365 Sales, Microsoft supplies a standard integration through Dataverse. For Salesforce, HubSpot and other products, you connect with a third-party connector or the Business Central APIs. Each has its own page on this site. So here we focus on the decisions that all of them share.

How we design a Business Central CRM integration

We begin with ownership rules. For every shared field, we write down where it is created, where it may be edited and which way it travels. Customer numbers and payment terms normally belong to the ERP. Lead source and sales stage belong to the CRM.

Next comes the moment of handover. Most companies create the Business Central customer only when a deal is won. That way, prospects never clutter the ledger. We define that trigger. We also define the checks that must pass, such as a tax ID or credit approval, and what happens when they fail.

What a finished Business Central CRM integration gives you

First, we match the records between the systems, after a cleanup of duplicates. From then on, changes sync on a schedule. A quote or order raised in the CRM appears in Business Central ready to fulfill. The prices on it come from the ERP in the first place.

You also receive the field mapping table and the ownership rules. You get a description of each scheduled sync job and a guide to the error list. With these, an administrator can see why a record did not transfer and fix it without calling a developer. Most errors turn out to be missing data.

Pitfalls that spoil a Business Central CRM integration

Dirty data is the main one. Suppose both systems hold the same company under three spellings. The sync will faithfully multiply the mess. So a matching and merging exercise before the first sync is unglamorous but necessary. We run it with your sales administrator, and it pays back quickly.

Two-way editing of the same field is the second. It sounds flexible, but it creates conflicts. The most recent save wins, and nobody knows why an address changed. One owner per field is simpler and far more dependable. The other side stays read-only. We recommend this.

Business Central CRM integration questions

Does Business Central have a CRM built in?

It has relationship management features covering contacts, interactions, campaigns, segments and opportunities. They suit companies with simple sales processes. Some teams need marketing automation, detailed pipeline forecasting or a mobile-first sales tool. These teams usually add a dedicated CRM and integrate it. We can tell you which group you fall into after a short look at how your sales team works today.

Which CRM integrates most easily with Business Central?

Dynamics 365 Sales, because Microsoft provides the integration as a standard feature with an assisted setup guide. Other CRMs connect well too, through connector apps or APIs. In that case, though, the mapping and upkeep are the job of the connector vendor or your partner. So weigh that extra work when you choose a CRM.

Should prospects be created as customers in Business Central?

Generally not. Keep prospects in the CRM until a deal is won. That keeps the customer list in the ERP clean. It also avoids posting setup for companies that may never buy. The integration then creates the customer at the agreed point. That is why we write the handover trigger down early, so every team knows when a prospect turns into a customer.

Can salespeople see invoices and payments in the CRM?

Yes. You can show posted invoices, open balances and order status on the account in the CRM. You can either copy them across or show them live. Sales teams often value this feature most. It prepares them for customer conversations, because they know what the customer owes before they dial. They also see which orders are late.

How is the integration maintained after go-live?

Someone should check the sync error list regularly. Also, test both systems together before major updates. We can take this on under a support arrangement. Or we can train your administrator to do it, with our notes. Either way, a Business Central CRM integration stays healthy when somebody owns it and looks at it often.

Pages for specific CRM products

This page covers the decisions that every Business Central CRM integration shares. For product-specific detail, see the pages below. They cover Dynamics 365 Sales, Salesforce, HubSpot and Dataverse. They also cover the contact features built into Business Central. Pick the page that matches your CRM, and then we can talk through your own mapping and ownership rules. For the product detail, see Synchronizing data in Business Central with Dataverse on Microsoft Learn.