Unified Operations & Dynamics AX Forum

• First off get a D365O LCS environment, your partner should have one and be working with you during this discovery.
• Use the LCS upgrade tool on your AX2012 Model Store to assess the impacts of your current code base against the changes in approach for D365O namely extension instead of overlaying.
• Through your partner get on the preview for the data upgrade tool so you can assess that element as well.

• Infrastructure analysis
• Environment planning
• Provisioning and configuration
• Fix / Merge code conflicts
• Test Base code

• Solution Gap Analysis
• Resolve functional design conflicts
• Business Design Validation
• Create new test scenarios

• Data Upgrade (smoke test)
• Data validation
• Data upgrade (2nd test) + Validation
• Data upgrade (3rd test) + Validation
• Integration Testing
• Cutover planning
• User acceptance test
• Training
• Cutover

• First off get a D365O LCS environment, your partner should have one and be working with you during this discovery.
• Use the LCS upgrade tool on your AX2012 Model Store to assess the impacts of your current code base against the changes in approach for D365O namely extension instead of overlaying.
• Through your partner get on the preview for the data upgrade tool so you can assess that element as well.

• Infrastructure analysis
• Environment planning
• Provisioning and configuration
• Fix / Merge code conflicts
• Test Base code

• Solution Gap Analysis
• Resolve functional design conflicts
• Business Design Validation
• Create new test scenarios

• Data Upgrade (smoke test)
• Data validation
• Data upgrade (2nd test) + Validation
• Data upgrade (3rd test) + Validation
• Integration Testing
• Cutover planning
• User acceptance test
• Training
• Cutover

Just a few comments on the migration conversation.  First, is about the data conversion.  For many this is the hardest piece of any system switch over.  This is especially true if you have even a medium amount of AX custom fields and files.    One approach to this challenge is avoiding the costs and complexities for converting the bulk of your data.   This is worth exploring with your partner or other firms in the market. 

Second is something some people are not focused on in their planning, reports.   You need to understand that the data source for your reporting changes with the Azure based D365 for Enterprise migration.   You cannot get at your core data any longer.   Microsoft has several options for this, with the most common of these solutions being Data Entities and O-Data access.   D365E comes with somewhere around 1,700 data entities to pull reports from. 

You can think of these Data Entities as separate data from your core system, a data mart that traditionally have had names like data warehouses, data cubes, data clouds, and now - data entities.  Regardless of the name and structure of this secondary data; you will need to pull reports from a completely new and different set of  data.    For many companies already through the upgrade process this has meant reprogramming virtually all of their custom reporting.  

There are various D365E paths, including ways around some of this redevelopment.  Regardless of whether you redevelop your reports or look for a solution that avoids parts of this, it is important to understand, define and budget this part of your migration to D365 for Enterprise.

Just a few comments on the migration conversation.  First, is about the data conversion.  For many this is the hardest piece of any system switch over.  This is especially true if you have even a medium amount of AX custom fields and files.    One approach to this challenge is avoiding the costs and complexities for converting the bulk of your data.   This is worth exploring with your partner or other firms in the market. 

Second is something some people are not focused on in their planning, reports.   You need to understand that the data source for your reporting changes with the Azure based D365 for Enterprise migration.   You cannot get at your core data any longer.   Microsoft has several options for this, with the most common of these solutions being Data Entities and O-Data access.   D365E comes with somewhere around 1,700 data entities to pull reports from. 

You can think of these Data Entities as separate data from your core system, a data mart that traditionally have had names like data warehouses, data cubes, data clouds, and now - data entities.  Regardless of the name and structure of this secondary data; you will need to pull reports from a completely new and different set of  data.    For many companies already through the upgrade process this has meant reprogramming virtually all of their custom reporting.  

There are various D365E paths, including ways around some of this redevelopment.  Regardless of whether you redevelop your reports or look for a solution that avoids parts of this, it is important to understand, define and budget this part of your migration to D365 for Enterprise.

Just a few comments on the migration conversation.  First, is about the data conversion.  For many this is the hardest piece of any system switch over.  This is especially true if you have even a medium amount of AX custom fields and files.    One approach to this challenge is avoiding the costs and complexities for converting the bulk of your data.   This is worth exploring with your partner or other firms in the market. 

Second is something some people are not focused on in their planning, reports.   You need to understand that the data source for your reporting changes with the Azure based D365 for Enterprise migration.   You cannot get at your core data any longer.   Microsoft has several options for this, with the most common of these solutions being Data Entities and O-Data access.   D365E comes with somewhere around 1,700 data entities to pull reports from. 

You can think of these Data Entities as separate data from your core system, a data mart that traditionally have had names like data warehouses, data cubes, data clouds, and now - data entities.  Regardless of the name and structure of this secondary data; you will need to pull reports from a completely new and different set of  data.    For many companies already through the upgrade process this has meant reprogramming virtually all of their custom reporting.  

There are various D365E paths, including ways around some of this redevelopment.  Regardless of whether you redevelop your reports or look for a solution that avoids parts of this, it is important to understand, define and budget this part of your migration to D365 for Enterprise.

Just a few comments on the migration conversation.  First, is about the data conversion.  For many this is the hardest piece of any system switch over.  This is especially true if you have even a medium amount of AX custom fields and files.    One approach to this challenge is avoiding the costs and complexities for converting the bulk of your data.   This is worth exploring with your partner or other firms in the market. 

Second is something some people are not focused on in their planning, reports.   You need to understand that the data source for your reporting changes with the Azure based D365 for Enterprise migration.   You cannot get at your core data any longer.   Microsoft has several options for this, with the most common of these solutions being Data Entities and O-Data access.   D365E comes with somewhere around 1,700 data entities to pull reports from. 

You can think of these Data Entities as separate data from your core system, a data mart that traditionally have had names like data warehouses, data cubes, data clouds, and now - data entities.  Regardless of the name and structure of this secondary data; you will need to pull reports from a completely new and different set of  data.    For many companies already through the upgrade process this has meant reprogramming virtually all of their custom reporting.  

There are various D365E paths, including ways around some of this redevelopment.  Regardless of whether you redevelop your reports or look for a solution that avoids parts of this, it is important to understand, define and budget this part of your migration to D365 for Enterprise.

Just a few comments on the migration conversation.  First, is about the data conversion.  For many this is the hardest piece of any system switch over.  This is especially true if you have even a medium amount of AX custom fields and files.    One approach to this challenge is avoiding the costs and complexities for converting the bulk of your data.   This is worth exploring with your partner or other firms in the market. 

Second is something some people are not focused on in their planning, reports.   You need to understand that the data source for your reporting changes with the Azure based D365 for Enterprise migration.   You cannot get at your core data any longer.   Microsoft has several options for this, with the most common of these solutions being Data Entities and O-Data access.   D365E comes with somewhere around 1,700 data entities to pull reports from. 

You can think of these Data Entities as separate data from your core system, a data mart that traditionally have had names like data warehouses, data cubes, data clouds, and now - data entities.  Regardless of the name and structure of this secondary data; you will need to pull reports from a completely new and different set of  data.    For many companies already through the upgrade process this has meant reprogramming virtually all of their custom reporting.  

There are various D365E paths, including ways around some of this redevelopment.  Regardless of whether you redevelop your reports or look for a solution that avoids parts of this, it is important to understand, define and budget this part of your migration to D365 for Enterprise.

Just a few comments on the migration conversation.  First, is about the data conversion.  For many this is the hardest piece of any system switch over.  This is especially true if you have even a medium amount of AX custom fields and files.    One approach to this challenge is avoiding the costs and complexities for converting the bulk of your data.   This is worth exploring with your partner or other firms in the market. 

Second is something some people are not focused on in their planning, reports.   You need to understand that the data source for your reporting changes with the Azure based D365 for Enterprise migration.   You cannot get at your core data any longer.   Microsoft has several options for this, with the most common of these solutions being Data Entities and O-Data access.   D365E comes with somewhere around 1,700 data entities to pull reports from. 

You can think of these Data Entities as separate data from your core system, a data mart that traditionally have had names like data warehouses, data cubes, data clouds, and now - data entities.  Regardless of the name and structure of this secondary data; you will need to pull reports from a completely new and different set of  data.    For many companies already through the upgrade process this has meant reprogramming virtually all of their custom reporting.  

There are various D365E paths, including ways around some of this redevelopment.  Regardless of whether you redevelop your reports or look for a solution that avoids parts of this, it is important to understand, define and budget this part of your migration to D365 for Enterprise.

Just a few comments on the migration conversation.  First, is about the data conversion.  For many this is the hardest piece of any system switch over.  This is especially true if you have even a medium amount of AX custom fields and files.    One approach to this challenge is avoiding the costs and complexities for converting the bulk of your data.   This is worth exploring with your partner or other firms in the market. 

Second is something some people are not focused on in their planning, reports.   You need to understand that the data source for your reporting changes with the Azure based D365 for Enterprise migration.   You cannot get at your core data any longer.   Microsoft has several options for this, with the most common of these solutions being Data Entities and O-Data access.   D365E comes with somewhere around 1,700 data entities to pull reports from. 

You can think of these Data Entities as separate data from your core system, a data mart that traditionally have had names like data warehouses, data cubes, data clouds, and now - data entities.  Regardless of the name and structure of this secondary data; you will need to pull reports from a completely new and different set of  data.    For many companies already through the upgrade process this has meant reprogramming virtually all of their custom reporting.  

There are various D365E paths, including ways around some of this redevelopment.  Regardless of whether you redevelop your reports or look for a solution that avoids parts of this, it is important to understand, define and budget this part of your migration to D365 for Enterprise.

Just a few comments on the migration conversation.  First, is about the data conversion.  For many this is the hardest piece of any system switch over.  This is especially true if you have even a medium amount of AX custom fields and files.    One approach to this challenge is avoiding the costs and complexities for converting the bulk of your data.   This is worth exploring with your partner or other firms in the market. 

Second is something some people are not focused on in their planning, reports.   You need to understand that the data source for your reporting changes with the Azure based D365 for Enterprise migration.   You cannot get at your core data any longer.   Microsoft has several options for this, with the most common of these solutions being Data Entities and O-Data access.   D365E comes with somewhere around 1,700 data entities to pull reports from. 

You can think of these Data Entities as separate data from your core system, a data mart that traditionally have had names like data warehouses, data cubes, data clouds, and now - data entities.  Regardless of the name and structure of this secondary data; you will need to pull reports from a completely new and different set of  data.    For many companies already through the upgrade process this has meant reprogramming virtually all of their custom reporting.  

There are various D365E paths, including ways around some of this redevelopment.  Regardless of whether you redevelop your reports or look for a solution that avoids parts of this, it is important to understand, define and budget this part of your migration to D365 for Enterprise.

Just a few comments on the migration conversation.  First, is about the data conversion.  For many this is the hardest piece of any system switch over.  This is especially true if you have even a medium amount of AX custom fields and files.    One approach to this challenge is avoiding the costs and complexities for converting the bulk of your data.   This is worth exploring with your partner or other firms in the market. 

Second is something some people are not focused on in their planning, reports.   You need to understand that the data source for your reporting changes with the Azure based D365 for Enterprise migration.   You cannot get at your core data any longer.   Microsoft has several options for this, with the most common of these solutions being Data Entities and O-Data access.   D365E comes with somewhere around 1,700 data entities to pull reports from. 

You can think of these Data Entities as separate data from your core system, a data mart that traditionally have had names like data warehouses, data cubes, data clouds, and now - data entities.  Regardless of the name and structure of this secondary data; you will need to pull reports from a completely new and different set of  data.    For many companies already through the upgrade process this has meant reprogramming virtually all of their custom reporting.  

There are various D365E paths, including ways around some of this redevelopment.  Regardless of whether you redevelop your reports or look for a solution that avoids parts of this, it is important to understand, define and budget this part of your migration to D365 for Enterprise.

Just a few comments on the migration conversation.  First, is about the data conversion.  For many this is the hardest piece of any system switch over.  This is especially true if you have even a medium amount of AX custom fields and files.    One approach to this challenge is avoiding the costs and complexities for converting the bulk of your data.   This is worth exploring with your partner or other firms in the market. 

Second is something some people are not focused on in their planning, reports.   You need to understand that the data source for your reporting changes with the Azure based D365 for Enterprise migration.   You cannot get at your core data any longer.   Microsoft has several options for this, with the most common of these solutions being Data Entities and O-Data access.   D365E comes with somewhere around 1,700 data entities to pull reports from. 

You can think of these Data Entities as separate data from your core system, a data mart that traditionally have had names like data warehouses, data cubes, data clouds, and now - data entities.  Regardless of the name and structure of this secondary data; you will need to pull reports from a completely new and different set of  data.    For many companies already through the upgrade process this has meant reprogramming virtually all of their custom reporting.  

There are various D365E paths, including ways around some of this redevelopment.  Regardless of whether you redevelop your reports or look for a solution that avoids parts of this, it is important to understand, define and budget this part of your migration to D365 for Enterprise.

Just a few comments on the migration conversation.  First, is about the data conversion.  For many this is the hardest piece of any system switch over.  This is especially true if you have even a medium amount of AX custom fields and files.    One approach to this challenge is avoiding the costs and complexities for converting the bulk of your data.   This is worth exploring with your partner or other firms in the market. 

Second is something some people are not focused on in their planning, reports.   You need to understand that the data source for your reporting changes with the Azure based D365 for Enterprise migration.   You cannot get at your core data any longer.   Microsoft has several options for this, with the most common of these solutions being Data Entities and O-Data access.   D365E comes with somewhere around 1,700 data entities to pull reports from. 

You can think of these Data Entities as separate data from your core system, a data mart that traditionally have had names like data warehouses, data cubes, data clouds, and now - data entities.  Regardless of the name and structure of this secondary data; you will need to pull reports from a completely new and different set of  data.    For many companies already through the upgrade process this has meant reprogramming virtually all of their custom reporting.  

There are various D365E paths, including ways around some of this redevelopment.  Regardless of whether you redevelop your reports or look for a solution that avoids parts of this, it is important to understand, define and budget this part of your migration to D365 for Enterprise.