Finance | Project Operations, Human Resources, ...

Import the historical Data to D365 new implementation

(0) Share

Report

Posted on by ahmed.kimo

536

Hello,

We have a new implementation D365 on Cloud with the default azure environments and our customer requested to import all of the transactions since 5 years (GL , PO , SO , FA , Payments ) .

My question we assume this is huge data to be imported and we will use Data Management for that , Is there any impact by importing this much data and dose the server with the default specs can have a big amount of data lie this or we have some limitations here ?

Also if the database is increasing every year by creating big number of transactions what will happen to the server and it's specs after some period or do we need to clean the data or shall we plan for increasing the server specs if we got the Database increased , if yes how we can plan for that ? tool for estimating or from LCS for example.

I have the same question (0)

All responses (8)

Answers (0)

ahmed.kimo 536 on at

Like (0)

Report

RE: Import the historical Data to D365 new implementation

Hi Nikolaos Mäenpää,

Your idea for integration also is good idea , It's seems that is very difficult to deal with D365 for the historical data and not recommended also ,moreover the new configuration it may effect the uploaded data behavior that may cause different result compared with the legacy system .

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

RE: Import the historical Data to D365 new implementation

Maybe you could create some simple integration to show transaction history for the selected customer, fetching data from the old system. This way the D365 user would not need to login to the old system.

How feasible this is, really depends on what type of data they need to check. For warranty I would imagine you mostly need item id, customer number, date of sales, not entire transaction history.

Was this reply helpful? Yes No
ahmed.kimo 536 on at

Like (0)

Report

RE: Import the historical Data to D365 new implementation

Hi Ludwig,

Thanks for your feedback ,

I will take a look on that also , Thanks

Was this reply helpful? Yes No
ahmed.kimo 536 on at

Like (0)

Report

RE: Import the historical Data to D365 new implementation

Hi André,

Thank you for your reply ,

Unfortunately the current system is not Ax2012 , and the reason behind importing data since 5 years is that all of the orders issued from our customer will be having warranty for 5 years also the statement of the open transactions since 5 year he is aiming to be generated from one place (D365) rather than looking into 2 different systems like customer statement or the maintenance for the sold products (i do not think they are in need for financial data for the previous years but since we are assuming sub-ledger will be imported then we will have ledger as well)

Sorry for long explanation but i'm trying to show you the full picture then you can suggest better solutions to convince our customer , Your advice is highly appreciated

Was this reply helpful? Yes No
ahmed.kimo 536 on at

Like (0)

Report

RE: Import the historical Data to D365 new implementation

Hi Ramit,

Thanks for your kind feeback ,

Could you please explain me what do you mean by discussing the database size with product team ? do you mean ticket through LCS or direct question to Microsoft Please advice

Can you please provide me the option in which i can use to clean up the staging data

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

RE: Import the historical Data to D365 new implementation

Hello ahmed.kimo,

In D365FO, Microsoft manages your machine and the performance. There are of course things you have to look out for but the volume of data recorded should not be a problem in general.

If you are still in double then I would recommend that you have a look at the TecTalks available on this forum. There are a couple that deal with environment setup, performance and alike.

Please see:

community.dynamics.com/.../techtalks

Best regards,

Ludwig

Was this reply helpful? Yes No
André Arnaud de Cal... 298,174 Super User 2025 Season 2 on at

Like (0)

Report

RE: Import the historical Data to D365 new implementation

Hi Ahmed,

If the previous system is AX2012. you can perform a database upgrade. If not, tt would be recommended to only move opening balances. If you want to import subledger details and GL, there is no way you will get it correctly if they also had e.g. currency revaluations.

Usually, the legacy system will be put in a read-only mode and history can be viewed in the old application.

What is the reason to have 5 years of full history in the new application?

Was this reply helpful? Yes No
Suggested answer

Ramit Paul 22,795 Most Valuable Professional on at

Like (0)

Report

RE: Import the historical Data to D365 new implementation

Hi,

We have seen no impact till date based on experience on country implementation.

1:However, its advisable you import outside of business hours to avoid slowness of the environment, because huge data import makes env slow.

2: For database size, I think you discuss this with product team if required.

3: Microsoft has out of box function to clean up notification, batch job history and staging data, so it is advisable to use these for free up space.

Was this reply helpful? Yes No