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

Index issues

(7) Share

Report

Posted on by BeastReturns_95

"I am performing a data migration from Dynamics NAV 2009 R2 to Business Central 27. In this process, when we select a modified table and manually compare it during the merging step, do we need to consider the index and its order?
For example, if we add an index in NAV 2009 R2, do we also have to create the same index in the same order in NAV 2013? I did not get any errors until the NAV 2013 stage, but when I moved to Business Central, I encountered some index-related errors."

Categories:

Dynamics 365 Business Central migration

Dynamics 365 Business Central

Microsoft Dynamics RMS

Microsoft Dynamics NAV

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

OussamaSabbouh 12,803 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hello,

Yes, you must merge keys (indexes) exactly, including field order, at every upgrade step.
If a table in NAV 2009 R2 had a custom index, that same index must exist in NAV 2013 → 2015 → 2018 → BC 27 with the same fields and order.

NAV sometimes ignores mismatches, but Business Central is strict.
If an index exists in metadata but not in SQL (or differs), BC will throw schema sync/index errors.
Fix the table definitions so all keys match across all versions, then re-sync.

Regards,
Oussama Sabbouh

1 people found this reply helpful.

Was this reply helpful? Yes No
BeastReturns_95 90 on at

Like (3)

Report
Copy link

Link copied!

@OussamaSabbouh can i get BC14 onprem to BC27 directly

Was this reply helpful? Yes No
Suggested answer

Kamal Khakhkhar 2,915 on at

Like (3)

Report
Copy link

Link copied!

Hii There ,

as per requirement if you just migrating the objects Its ok to go direct as per like this but if you migrating data also then there is defined cycle you need to go through upgrade matrix as per requirement.

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-v14-v15-compatibility

https://community.dynamics.com/forums/thread/details/?threadid=af59c1e6-b7d6-4e4b-a2db-b12b40a194e6

You can Check the reference links ,
if you found answer Mark It Answered.

Thank You.

Kamal Khakhkhar

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Jainam M. Kothari 15,732 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

Yes, you must replicate custom indexes and maintain their order during NAV-to-Business Central migration because BC enforces stricter schema validation than older NAV versions. While NAV 2009 to 2013 upgrades often tolerate missing or reordered indexes, Business Central checks key definitions and composite key order, so mismatches can cause upgrade errors or performance issues.

The best practice is to identify all custom indexes in the source, recreate them in the target schema with the same order, and validate before schema synchronization.

1 people found this reply helpful.

Was this reply helpful? Yes No
Gerardo Rentería Ga... 25,555 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi, good day
I hope this can help you, and give you some hints.

Upgrading to Dynamics 365 Business Central 2025 release wave 2 - Business Central | Microsoft Learn

Best Regards
Gerardo

Was this reply helpful? Yes No
Suggested answer

Saurav.Dhyani 14,419 User Group Leader on at

Like (2)

Report
Copy link

Link copied!

You cannot do directly to BC 27.

From NAV 2009 R2 here is your upgrade path:

NAV 2009 R2 - NAV 2015 - BC 14 - BC25 - BC27.

Regards,

Saurav Dhyani
https://www.youtube.com/@sauravdhyani?sub_confirmation=1

1 people found this reply helpful.

Was this reply helpful? Yes No