Small and medium business | Business Central, N...

Does the synced records between D365 sales and BC share the same GUID?

(6) Share

Report

Posted on by MRVIX

1,421

I'm having issues syncing Products and Sales Orders from D365 Sales to BC. I wonder if manually migrating the records will fix my issue. Does the synced records between D365 sales and BC share the same GUID?

Categories:

Dynamics 365 Business Central

Dynamics 365 Business Central migration

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Pallavi Phade 3,721 on at

Like (3)

Report

Namaste @MRVIX

No — D365 Sales (Dataverse) and Business Central do not share the same GUIDs. GUID is autogenerated individually in the the respective apps .

Manually migrating the records to BC does not create Integration Links . You have to migrate as per integration table mappings -fields and ensure all is updated . Check Boolean Field "Coupled"

Warm Regards

Pallavi Phade

Was this reply helpful? Yes No
Suggested answer

Aman Kakkar 2,241 on at

Like (4)

Report

Hi,

Short answer: No — they do NOT share the same GUID, and manually migrating data will not fix sync issues (and may make things worse).

Hope this helps.

Aman K

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 5,073 on at

Like (2)

Report

Hello,

Each system generates its own GUID. The integration links records through mapping fields, not shared IDs.

Will manual migration fix sync issues?

Usually no.
Manually migrating won't align GUIDs and can make mapping conflicts worse.
Fixes normally involve checking item numbers, integration mappings, and re-coupling.

If you want, I can guide you through the quickest checks.

Regards,
Oussama Sabbouh

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Jainam M. Kothari 15,627 Super User 2025 Season 2 on at

Like (1)

Report

Hello,

No, synced records between Dynamics 365 Sales and Business Central do not share the same GUID; each system uses its own unique identifier (Sales uses entity GUIDs, BC uses SystemId).

The integration relies on a mapping table in BC to link records, so manually migrating data won’t create these links and could lead to duplicates or broken sync.

Instead, use the Dataverse integration and, if needed, match-based coupling to connect existing records properly.

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,309 Super User 2025 Season 2 on at

Like (1)

Report

If you don't use the standard connector, you can synchronize the GUID to the BC.

For example,

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

https://yzhums.com/64775/

Hope this helps.

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

Rishabh Kanaskar 6,147 on at

Like (2)

Report

Hi,

No, manually migrating records will not fix the GUID issue. The integration between D365 Sales and Business Central uses Dataverse to maintain relationships, and synced records do not share the same GUID across systems. Each system has its own primary key

Thanks

Rishabh

Was this reply helpful? Yes No