Data Migration

 

Data Migration

Data is one of the most important aspects in the adoption and success of a project. As companies grow and technologies shift, managing data has become an extremely complex and critical task. For companies moving from an on-premise system to Microsoft’s cloud-based Dynamics 365 for Finance and Operations, Microsoft provides the Data Management Framework (“DMF”) tool to assist customers with data migration for D365

 

Master data spans the dimensionality of an organization’s business functions, and consists of information about a person, entity or object. Master data can be very detailed. For example, a master vendor record contains not only general information such as a vendor’s name and address, but also specific information, such as payment terms and delivery instructions. Master data remains somewhat constant over time and is really the core data about your company which forms the basis of an enterprise-wide “system of record” for the business.

 

Transactional data will consist of “facts” like quantities shipped, amounts invoiced and hours worked, and be associated with the master data dimensions. The volume of transactions grows exponentially each year and can easily add up to millions of records. Transactional data can be either closed historical transactions or open transactions. Transactional data are all the unique business events that occur in the day-to-day operations of a business, such as a shipped order or a movement of inventory.

 

Master Data:

Customers

Vendors

Products

Released Products

Product Costs

Bill of Materials

Routes

Employees

Contractors

Projects

 

 

 

 

 

 

 

 

Transactional Data:

Purchase orders

Fixed assets

Fixed asset Transactions

Open AP

Open AR

GL Balances

Outstanding Checks

Counting journals

Movement journals

Purchase agreements

 

 

The Jobs for entities could be run in batches for which we could configure the threshold parameters by setting value in Configure entity execution parameters.

 

 

 

 

 

 

 

Let us get to know the entities for Master data:

Master data Load	Entities
Vendors	Vendors V2
Vendor bank account	Vendor bank accounts
Customers	Customers V3
Customer bank account	Customer bank accounts
Vendor postal address	Vendor postal addresses
Customer postal address	Customer postal addresses
Dimensions	Colors, Sizes, Styles
Products	Released product creation V2
Released products	Released products V2
Released product variants	Released product variants V2
Masters	Product master styles Product master colors Product master sizes
Product costs	Pending item prices
Cost Group	Cost group
Cost category	Cost category
Employees	Titles Jobs Employee Contractor Positions V2 Position hierarchies Position worker assignments
BOMs	Bill of materials headers Bill of materials versions V2 Bill of materials lines V2
Resource	Resource groups Resource group calendar assignments Operations Operation Resource Resource calendar assignments Resource group membership
Route	Route headers Route Versions Route operations V2 Route operation properties V2 Resource requirements for route operation properties
External item description	External item descriptions for vendors
Item coverage	Item coverage
Default order settings	Product default order settings
Party Contacts	Party contacts
Product category assignments	Product category assignments
Approved vendors for variants	Approved vendors for variants
Approved vendors for products	Approved vendors list by products
Fixed asset	Fixed assets
Fixed asset book	Fixed asset book V2
Projects	Projects

 

Transactional Data	Entities
Purchase orders
Open AP	General journal
Open AR	General journal
GL balances	General journal
Outstanding checks	General journal
Fixed asset transactions	Fixed asset journal V2 entity
Movement journal	Inventory movement journal headers and lines
Counting Journal	Inventory counting journal lines
Purchase agreements	Trade agreement journal table V2 Open purchase price journal lines
Project transactions	Project journal lines for cost/sale beginning balances

 

 

Get started:

·       Must make sure if the data mapping is right

·       Identify issues like naming conflicts and data integrity

·       Do it incrementally and get verification from business

·       Sequence of the load should be right

·       Setup data and reference data should be available

·       Environments in Sync

·       Report on the issues

 

Volume:

·       Assess the amount of data you need to move and factor this into planning

·       Use the phased approach for testing and to minimize system downtime

·       Estimation for the load will be helpful