What Exactly does Microsoft’s Migration Tool contain?

·        Setup and installation: ledger, client groups, seller classes, etc..

·        Master information: customer, vendor, job, accounts, etc..

·        Open documents, pending invoices, etc: sales order, purchase order, AR invoices, etc..

·        System Configuration: number sequences, users, user groups, protection, etc..

 Ideally, We would not recommend migrating historical transactions. But if you wanted to hang on to them you can leave an example of the older system running or get the information from a data warehouse. That having been said, there are certainly some circumstances in which losing this information is not perfect  especially if you want to get customer order history to take complete advantage of being an Sunbridge Software services organization. If that's the case, let's talk and work out the best solution for your company.

However, Back to a more standard migrations. The short and long of it's basically anything which has an entity could be migrated to Microsoft Dynamics 365 with the support of this AX 2009 migration tool. It sits right interior of AX 2009 and supplies several solutions to assist you through the process Such as the added data migration checklist. The checklist provides an easy to follow process which walks you through everything. For instance, through the migration you will define data conversion principles and consider how data might need to change within the move due to data model changes. Inside the checklist, after that you can easily set which legal entities you'll include or exclude in the conversion.

Here's A snapshot of what we saw at AXUG 2016 in Tampa.

Defining data entry mappings by module, and whether or not they will be contained in the migrations. If that sounds daunting, do not worry. You don't have to move the entire system at once. The AX 2009 migration tool lets you chunk up the work by authorized entities, data entities, and much more.

The final steps on your route to Dynamics 365 start with defining the migration groups along with the set of entities That will be part of the export package (for example, maybe start with only a Special customer group). Next, you'll review the area mappings sources and targets. Then the finale you click the export button and watch the magic happen. You'll get a complete package that is ready to easily import into Dynamics 365.