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

Can a Dynamics 365 Sales Account create a BC Company Contact instead of a BC Customer?

(2) ShareShare
ReportReport
Posted on by 126

Dynamics 365 Sales Account → Business Central Company Contact instead of Customer

I would like to configure the integration between Dynamics 365 Sales and Business Central as follows:

  • When a new Account is created in Dynamics 365 Sales, I do not want it to automatically create a Customer in Business Central.
  • Instead, I would like it to create a Contact of type Company in Business Central, without any Customer linked to it.
  • The company would remain a prospect at this stage.
  • Later, when the prospect actually becomes a customer, I would use the standard Create as Customer function in Business Central to create the Customer from the Company Contact.
  • At that point, I would like the newly created BC Customer to be coupled to the same existing Account in Dynamics 365 Sales, without creating a second Account and without losing the existing CRM activities/history.

So the intended flow is:

Sales Account → BC Company Contact → BC Customer

while keeping one single Account in Dynamics 365 Sales throughout the entire process.

Is this scenario possible in Business Central 28 using only Integration Table Mappings / Integration Field Mappings, without AL customization?

In particular, can the same Dataverse Account first be coupled to a BC Company Contact and later also be coupled to the BC Customer created from that Contact, without causing conflicts with the standard Customer–Account integration mapping?


 

  • Suggested answer
    OussamaSabbouh Profile Picture
    20,172 Super User 2026 Season 2 on at

    Hello Gianardi,

    Not fully with standard mappings alone. In the standard Dynamics 365 Sales integration, Dataverse Account ↔ BC Customer, while Dataverse Contact ↔ BC Contact, and Microsoft’s standard Contact mapping specifically handles BC Person contacts, not Company contacts; BC 28 lets you create additional table/field mappings, so you could technically create a custom Account → BC Company Contact prospect mapping, but mappings are static and there is no standard mechanism that, when you run Create as Customer, transfers that coupling from the Company Contact to the newly created Customer. I also would not keep the same Account simultaneously coupled through both a custom Contact–Account mapping and the standard Customer–Account mapping because you then have two synchronization mappings acting on the same Dataverse row. The safest no-code/manual design is therefore: Account (Prospect) → Company Contact, then when converted use Create as Customer, remove the prospect Contact coupling, change the Dataverse Account Relationship Type to Customer, and manually couple the new BC Customer to that same existing Account; this preserves the CRM Account and all its activities/history without creating another Account. If you want that handoff to happen automatically, you need customization/automation beyond Integration Table/Field Mappings. 

    Regards,
    Oussama Sabbouh

  • Suggested answer
    YUN ZHU Profile Picture
    103,702 Super User 2026 Season 2 on at

    As far as I know, this cannot be achieved out of the box because these tables were designed with a 1-to-1 relationship. You can consider custom development, or use the approach below to send data directly to Dataverse.

    Dynamics 365 Business Central: Integrate with Microsoft Dataverse via APIs (Not using the standard Dataverse connector)

    https://yzhums.com/64775/

    PS: Dynamics 365 Business Central Blog Series: Integrate with Microsoft Dataverse

    https://yzhums.com/63916/

     

    Thanks.

    ZHU

     

  • Suggested answer
    Grigorios Mavrogeorgis Profile Picture
    3,666 Super User 2026 Season 2 on at

    Hi, the first part is pure setup. On the CUSTOMER integration table mapping set Synch. Only Coupled Records to Yes, then new Accounts stop creating customers in BC and only the ones you couple yourself will sync.

    The rest needs an extension. There is no standard mapping from Account to a BC company contact, the Contact table is already used by the CONTACT mapping against Dataverse contacts, and the new mapping wizard doesn't offer a table that is already mapped.

    Coupling one Account to two BC records is not a good practice, even if it goes in you then have two mappings writing to the same Account and you'll have sync errors later.

    What usually works is leaving the prospect only in Sales, then coupling the customer manually at the moment it converts, so the Account and its history stay the same one. 

    Glad to help - follow up if anything is unclear.   

    ►  If this solved it, marking it verified helps others too.       

    Regards,
    Grigorios Mavrogeorgis
    Business Central Consultant & AL Developer

    Work: Gmsoft Limited
    Blog:  insidebusinesscentral
    LinkedIn: linkedin.com/in/gregorymavrogeorgis

     

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

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

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 765 Super User 2026 Season 2

#2
YUN ZHU Profile Picture

YUN ZHU 571 Super User 2026 Season 2

#3
Grigorios Mavrogeorgis Profile Picture

Grigorios Mavrogeorgis 299 Super User 2026 Season 2

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans