We are seeing more and more users getting up to speed for future migration of Microsoft Dynamics GP data, into Dynamics Business Central (BC) in the cloud, and want to be sure your data is in the best state possible for a smooth migration. I would like to call out the data we currently migrate, from Dynamics GP to Dynamics BC, and how you can insure the Dynamics GP data is ready for your initial Cloud Migration:
As of May 2020, we will migrate the following data points from Microsoft Dynamics GP:
- Chart of Accounts master records – You can include Dynamics GP Account segments as Dimensions. Business Central uses your Main Segment as the G/L Account Number, and the other segments will be considered Dimensions. During the migration you can choose which two segments will be the Global Dimensions inside Business Central; these can be used throughout Business Central in reporting and in transaction entry pages.
- General Ledger account balances – we bring over a monthly balance amount for each month of each year, open and historical.
- Customer master records.
- Outstanding transactions from Receivables Management.
- These transactions will be brought in with the amount remaining in Dynamics GP. For example, if an invoice for $1000 was entered into Dynamics GP, and it has been partially paid and has a remaining balance of $400, the new invoice created in Business Central will be for $600 as that is the amount remaining to be paid. We bring over all transaction types from Receivables Management.
- Vendor master records
- Outstanding transactions from Payables Management.
- Inventory items – quantity on hand, by site/location at the time of migration as well as the cost associated with all inventory layers.
- All Serial and Lot tracking information, by item and associated quantities.
- Service items are automatically assigned the FIFO valuation method.
- Historical data from Receivables, Payables, Sales Order Processing, Purchase Order Processing, and Inventory – to see this in BC, for example, Sales would be found under Customers>All and you will see all GP options:
I suggest running thru the following steps in Dynamics GP before you attempt the migration to Dynamics BC for the first time.
Dynamics GP good practices for data migration
- Verify your GL data is in good standing, by running the following scripts to insure there are no unbalanced transactions:
SELECT JRNENTRY AS ‘WORK JOURNAL ENTRY’, SUM(DEBITAMT) AS ‘TOTAL DEBITS’, SUM(CRDTAMNT) AS ‘TOTAL CREDITS’ FROM GL10001, GL00100 WHERE GL10001.ACTINDX = GL00100.ACTINDX and GL10001.ACCTTYPE = 1 GROUP BY JRNENTRY HAVING SUM(CRDTAMNT) <> SUM(DEBITAMT)
SELECT JRNENTRY AS ‘OPEN YEAR JOURNAL ENTRY’, SUM(DEBITAMT) AS ‘TOTAL DEBITS’, SUM(CRDTAMNT) AS ‘TOTAL CREDITS’ FROM GL20000, GL00100 WHERE GL20000.ACTINDX = GL00100.ACTINDX and ACCTTYPE = 1 GROUP BY JRNENTRY HAVING SUM(CRDTAMNT) <> SUM(DEBITAMT)
SELECT JRNENTRY AS ‘HISTORY YEAR JOURNAL ENTRY’, SUM(DEBITAMT) AS ‘TOTAL DEBITS’, SUM(CRDTAMNT) AS ‘TOTAL CREDITS’ FROM GL30000, GL00100 WHERE GL30000.ACTINDX = GL00100.ACTINDX and ACCTTYPE = 1 GROUP BY JRNENTRY HAVING SUM(CRDTAMNT) <> SUM(DEBITAMT)
If results are returned in any of these scripts, they will need to be researched and corrected, before proceeding. A support case with the Dynamics GP team may be needed if you are unable to correct the results that are damaged.
- Run the following to see if you have invalid records in your period setup. If you do, they can be removed, or you can submit a support case with the Dynamics GP team for assistance on the removal of them:
SELECT * FROM SY40100 WHERE PERIODDT=’1900-01-01′ OR PERDENDT = ‘1900-01-01’
- When the scripts from step 1 are returned with no results, navigate to Financial >> Utilities >> Financial >> Reconcile and start with the oldest open year, and reconcile each, until you get to the last year you have entered.
- You must have all posting accounts set up under Administration >> Setup >> Posting >> Posting Accounts. We will not look to where modules/documents/items are pulling posting accounts from, and only use what is set up under the default posting account setup. If they are not set up, the migration to Dynamics BC will error, and appear to have unbalanced transactions because it will not be able to find the corresponding posting accounts.
- Be sure your MAIN account segment is defined in Dynamics GP. You can check this under Administration >> Setup >> Company >> Account Format – Main Segment ID.
- Verify there are no gaps within your fiscal period setup. You can check this under Administration >> Setup >> Company >> Fiscal Periods. What you are verifying is that all periods and days are accounting for, in each year that you currently have in Dynamics GP.
- Verify you have no Inventory items that exceed 20 characters in their name. To do so, run the following script in SQL:
SELECT ITEMNMBR FROM IV00101 WHERE LEN(ITEMNMBR) > 20
- If you do get results, these items will be truncated to 20 characters so it would be in your best interests to address these items before you migrate to get them under 20 characters. If you have items to address, you can use PSTL in GP to change those items. If you are unsure how to proceed, please submit a case to the GP Support Team for assistance.
At this point, you are ready to attempt the Dynamics GP to Dynamics BC migration and see if you get errors, or if the data is migrated successfully. Happy Migrating!