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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Upgrade Project AX 2012 to D365 FO estimation sheet

(0) ShareShare
ReportReport
Posted on by 66

Hi ,

I am working on a upgrade project and have uploaded the model file in LCS and got the excel estimate .

What I find is that the excel estimate sheet is having very less estimation for the conflict objects specified.

Eg. InventUpd_Reservation is showing a conflict and the estimation is just 10 mins and same is the case for other different objects.

I am sure that this is not the correct estimation as I have worked previously for fixing code upgrade tasks in Ax 2012 upgrade projects.

If I take the same object and asked to customize with similar functionalities then the same would have taken 8-12 hours int he case of  "InventUpd_Reservation".

Can anyone help me with that is the proper way to estimate the work for this objects.

Is there a way to find the proper estimation ?????

I have the same question (0)
  • Verified answer
    Martin Dráb Profile Picture
    237,801 Most Valuable Professional on at

    You can go and change the numbers if you think that the average number should be different, or if you're aware of some objects will take longer than the rough estimate says.

    Note that it's impossible to guess how much work is needed without knowing what kind conflicts are there. For example, there may be a single line of code to fix in InventUpd_Reservation and you'll solve it in a minute. Or there is a huge amount of conflicts and your developers are not experienced with upgrades, therefore it'll take ten hours. It's impossible to say without more information.

    The spreadsheet don't say that upgrading InventUpd_Reservation will take ten minutes - it says that an average would be ten minutes, because some conflicts will take almost no time and some a lot. You can fiddle with the average time, add your own estimattion... or accept that it's not meaningful and stop paying too much attention to it.

  • vicky1234 Profile Picture
    66 on at

    thanks Martin,

    Its quite un realistic estimation that the excel provides which Microsoft should rework on as it gives a very wrong impression to the technicals doing the upgrade for the first time as they think MIcrosoft provides better accuracy.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 660 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 549 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 307 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans