Finance | Project Operations, Human Resources, ...

Upgrading to D365 FO consideration

(1) Share

Report

Posted on by Axel Cage

311

Hello friends,

Anyone can advice me a consideration when we want to Upgrade from older version of D365, it may from AX. Or perhaps if it is from another system, not AX / D365 FO. what strategy and things to consider ? is there tools for it ? what about the code conversion and data conversion that obviously will not be under same structure.

Understand that this is wide topics, is there a good and complete resources about it ? video with presentation will be better. I found some while googling, but very short (less then 5 min) So looking for some recommendation from all of you who already experienced on this.

Thanks in advance.

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Suggested answer

BillurSamdancioglu 20,825 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!

Hi,

Yes there are tools and strategies to use.

This link will help you.

learn.microsoft.com/.../upgrade-overview-2012

Was this reply helpful? Yes No
Suggested answer

Charlotte X Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi Axel Cage,

I haven't tried it, but I think the link provided by Billur is very useful.

The following documentation is supplemented, you can also refer to it.

Upgrades, updates, and hotfixes resources - Finance & Operations | Dynamics 365 | Microsoft Learn

Was this reply helpful? Yes No
Martin Dráb 239,385 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Note that the three scenarios you mentioned are very different; a migration from a different system isn't even an upgrade at all.

I think you should decide what you actual want before looking for more information, because information about - for example - installing a platform update is useless for planning a new implementation of F&O for a customer migrating from Navision.

Was this reply helpful? Yes No
Axel Cage 311 on at

Like (0)

Report
Copy link

Link copied!

Hi all,

Appreciate these. I really would like to see the usage about all the tools that we're using for the migration project. For example during starting, we being advised to having "Standard migration assesment", if my understanding is correct, then the 1st point which is Functional and business assessment was done by interviewing / direct information gathering.

But for the 2nd point is Technical assessment and tools, wonder if there is some demo about this so we can see the real result. Also there is a code upgrade tools, this one I heard from D365 Techtalk. but unfortunately there is no demo for it.

Thanks in advance,

Was this reply helpful? Yes No
Axel Cage 311 on at

Like (0)

Report
Copy link

Link copied!

Hi Martin,

Yes, I understand on that. Only currently we also haven't decided, even about data, yet to decide upgrade or migrate. In some techtalk video, it was suggested, better to do data migration then because some schema also changed. This is the part we want to learn first.

Btw, back to the assessment part, any sample of how the result assessment document looks like ? Because it is stated here Standard migration assessment | Microsoft Learn and it looks very important as I'm thinking this is like the guidelines, blueprint of every upgrade/migrate project should produced.

Thanks,

Was this reply helpful? Yes No
Martin Dráb 239,385 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Whether it's a migration or an upgrade isn't your choice - it depends on the nature of your project. For example, if you're now using a different system, such as Navision, and you want to switch to F&O, it's not an upgrade of F&O. On the other hand, if you're upgrading from a an older version of F&O to the latest one, it's an upgrade and talking about things like migration assesment makes no sense.

Was this reply helpful? Yes No
Suggested answer

CU22041105-0 8 on at

Like (0)

Report
Copy link

Link copied!

Upgrading to D365 FO is not a direct upgrade, it’s a reimplementation.

Key things to consider:

Code → AX/custom code won’t carry over. You’ll need extension-based redevelopment
Data → Migrate only clean master data + open transactions
Tools → Use LCS + Upgrade Analyzer for assessment and planning
Customization → Reduce it. Stick close to standard to avoid future issues
Process review → Don’t copy old system. Redesign where needed
Testing → Critical (UAT, performance, integrations)

Strategy:
Start with assessment → fit-gap → data cleanup → phased implementation → strong testing.

Was this reply helpful? Yes No