Hi all,
I am still using the AX 2012 R3. Our system is slightly customized. Since we AX is running out of support we are thinking about migrating to 365.
and here I go with some basic questions since I am new at this.
1. Can we migrate our system by ourselves?
2. If so. What is the complexity of moving Business DB and Model DB?
3. Do we need to subscribe to the migration assessment plan if we want to move to 365 or only the subscription will be enough.
4. every customization has to be "re-customized?"
5. any additional information to understand the migration process will be very helpful
Thanks a lot for your kind reply guys,
thanks a lot before hand, hope to hear from you soon.
It is working now that I did follow the instructions on that link. I have received the Excel report from LCS code Upgrade.
I think I can get along.
thanks for your support Nathan
Ok maybe I know why... Here some info that I will try and let you know
hi Nathan,
In Project Settings there is no Visual Studio Team Services but there is an Azure DevOps tab where I add the Azure DevOprs Site URL and DevOps Project with project template. In the other hand I created a new Organization in Azure DevOps with a project of time VST instead of Git (that is what caused the issue the first time).
but.... now when running the code upgrade service and by uploading my ModelStore.zip I get another error that says:
"We're sorry, the analysis can't be completed. To research this issue, see Find Support."
So I am not sure now what do I have to do to get the report about my AX2012
again Any help is greatly appreciated
Hey Nestor, please Go to Project Settings\Visual Studio Team Services to configure your Visual Studio Team Services site URL and project name. You, the actor running the process, will have to (I think) project admin for the current project as well as the agility to create a TFVC repo. Additionally, i think there is a high likelihood you'll get an "error" that states work items couldn't be created. This can be ignored.
HI Nathan,
Thanks a lot for your fast reply,
I been reading about it, and I am trying to make some kind of testing But I got lost along the way.
I have uploaded my ModelStore.Zip to Cope upgrade in LCS but I get this error when analizing:
The Visual Studio Team Services project is not found. Please verify the Visual Studio Team Services settings then retry. More information: There is no team project named 'AX2012R3 to Dynamics365' in source control..
I have created an Azure DevOps project called : AX2012R3 to Dynamics365' and attached the Personal Access Token link to LCS but I do not know where to add the Visual Studio Team Services??
Again I really appreciate your kindly help
thanks a lot!
Hey Nestor. I'll do my best to answer your questions. There is a lot of additional documentation that can be viewed to get more detail.
1. yes. There is a specific process MSFT has to follow to upgrade your AX 2012 database into F&O. Having a partner that has done this process before would be helpful. links with more info are docs.microsoft.com/.../data-upgrade-2012, docs.microsoft.com/.../prepare-data-upgrade, docs.microsoft.com/.../replication-setup
2. There is only a transactional DB now. There is a specific upgrade process to follow so complexity is variable and determined by your environments number of ISVs, customizations, age, if you upgraded from AX 2009 or an earlier version and so on.
3. I don't believe so. I'm not sure what you specifically are asking about with the migration assessment plan. In order to start your project inside LCS, you will need the minimum license procurement which I believe in 20 licenses for F&O.
4. Code is now based on an extension model so potentially. any net new elements can be upgraded. any changed to MSFT objects will need to be reviewed. MSFT inside LCS has upgrade tooling to help get your code form AX 2012 to F&O but it only helps the process - it doesn't do all the work for you. This tooling can also provide you an estimate on your code upgrade with details.
5. clean up your 2012 environment as best you can. clean out any data that isn't needed using OOTB clean up tools. remove any customizations that are no longer needed if possible and practical. I think you can create your own LCS project to run the upgrade analysis and tooling for code upgrade which may be helpful.
André Arnaud de Cal...
291,969
Super User 2025 Season 1
Martin Dráb
230,842
Most Valuable Professional
nmaenpaa
101,156