Finance | Project Operations, Human Resources, ...

Migration tool for migrating Huge amount of data from Azure SQL Database to Dynamics 365 Finance and Operations

(0) Share

Report

Posted on by Community Member

We have to migrate huge volume of data from Azure SQL database to Dynamics 365 Finance and Operations Entities. We are considering the below options.

1. Using a combination of Logic Apps and D365 Data Mananagement- Data import jobs to migrate the entities. However here the process is asynchronous and we wouldn't have much control on the same for error handling and restartability. Also for every migration , we will need to put the data for a single entity in a zip (package) with a fixed naming convention and manifest and package header files.

medium.com/.../logic-app-integration-with-d365-f-o-524ac4909f0

2. In second approach, SSIS packages will be used to load data using custom D365 connector (Kingwaysoft connector). .https://www.kingswaysoft.com/products/ssis-integration-toolkit-for-microsoft-dynamics-365/help-manual/ax/destination. This connector converts the data format to OData which is recognizable by D365. This approach has a limitation of loading 100K records at a time.

Which of these 2 approaches is recommended.

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Adrian Begovich 1,027 Moderator on at

Like (0)

Report

Hi Manish Pradhan,

I would take the SSIS approach.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Adrian. Seems that SSIS is better suited and doesn't involve setup at the D365 side. Could you please share your rationale for suggesting SSIS over the Logic APPS +DMF combination.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Adrian, Would be helpful if you could please share some comparison or the reason for suggesting SSIS over DMF for the Data migration based on your experience. Thanks.

Was this reply helpful? Yes No
CJustin 262 on at

Like (0)

Report

I would suggest you use the SSIS approach as you would need not setup Dynamics 365 connector as you already use the D365 connector to convert the data to format recognizable by Dynamics 365.

The first method is not suitable as it is Asynchronous and you do not have control if it heads in the wrong direction.

I hope this helps!

Regards.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

The SSIS approach is much better as there would be no need to configure it from the Dynamics 365 end.

Also this approach allows more control over data transition.

And there are no deviating processes happening in the background.

Was this reply helpful? Yes No