What is the database structure during a migration in Business Central?
In this video, we will run through the database structure during a migration process using the Migration Toolbox.
First of all, let’s see what we call the different companies.
The live company is the name we use for the company, which is always the current company you do postings in, so the company you actually use is always named the Live company.
In a workshop with a customer before starting a migration process, we create what we call a workshop company.
This is a company meant to be deleted and it’s only temporary to show what we can do in a new company in the new version of Business Central.
The go-live company is the name we place on the new company on which we intend to eventually go live.
So, rather early in the process, we start working on the go-live company where we add only correct data.
If you want to test Master Data that we move, we make a copy of the go-live company, which we call go-live copies.
And in those companies, you can do all the testing, all the posting and check out the processes that are being designed in the process.
So, the go-live company will always be the same company heading forward to go-live, and after go-live, the go-live company will turn into the new Live company.
Let’s look a little more in details how this works.
So, first of all, we create a new company in the new Business Central solution.
This is done with the standard setup.
After that, we extract data from the old database either if it’s an old NAV-database or whatever ERP system, we extract data and map it into Excel sheets to be able to import data.
On top of the new company, we import that data, but in copies of the company, so, it’s possible for the client to see, if the data is correct, or if there are mistakes in the data, so, it’s possible to do new copies all over – to do this testing.
After the testing is done and the client says the data looks correct, it will be put into the go-live database in the correct order, so the go-live database will not be destroyed.
This means, the go-live database can exist during the entire upgrade process.
Finally, we will do the batch job for go-live in the go-live company.
And this means, that the go-live company was actually the same company from the beginning.
So it’s very important to understand, that the go-live company is being enriched during the entire process.
And if you want to test things and try out things, you will have to do it in copies of the go-live company.