web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Qualified Lead Accounts & Contacts Not Syncing from CRM to BC

(3) ShareShare
ReportReport
Posted on by 328

Hi Everyone,

I am currently working on the integration between Dynamics 365 Sales CRM and Business Central.

The synchronization Job Queue is running successfully every 5 minutes. However, when I qualify a Lead in Dynamics CRM, the qualified Lead records (Accounts and Contacts) are not getting created in Business Central.

Additionally, I noticed that the CRM Account data is also not getting stored in the mediator table in Business Central (Account Dataverse table).

The Job Queue continuously shows “1 Unchanged” every time, and no records are being created in BC.

At the same time, if I create an individual Contact or Customer directly in CRM, the synchronization works properly and records are successfully created in BC.

So currently, the issue only occurs with records created through Lead Qualification.

Does anyone know why the qualified Lead (Accounts and Contacts) records are showing as “Unchanged” instead of syncing to BC and why the data is not getting inserted into the Account Dataverse mediator table?

WhatsApp Image 2026-05-20 at 4.17.22 PM.jpeg
I have the same question (0)
  • Suggested answer
    OussamaSabbouh Profile Picture
    15,861 Super User 2026 Season 1 on at
    Hello,
    This usually means the records created by Lead Qualification do not meet the BC integration mapping/filter rules, or BC is set to sync only coupled records. In Business Central, check Integration Table Mappings for CUSTOMER / CONTACTS / Dynamics CRM Account and verify: Sync. Only Coupled Records is not blocking new records, the sync direction allows From Integration Table / Bidirectional, and the Integration Table Filter does not exclude qualified-lead-created Accounts/Contacts. Microsoft notes that new Dataverse rows are only created in BC when the mapping allows uncoupled records to create destination records; otherwise the job can run successfully but show unchanged/skipped behaviour. Also compare a CRM Account created manually versus one created from lead qualification: fields like account type/customer type, required template fields, owner, company id, status, or custom filters may differ, so BC sees the qualified Account but does not consider it eligible for the CUSTOMER mapping.
    Regards,
    Oussama Sabbouh

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,034 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,199 Super User 2026 Season 1

#3
AndrewThomas81 Profile Picture

AndrewThomas81 1,080

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans