Hi @dpjat 

I know it isn’t the newest 6xxx release but many of the suggestions is valid still.

https://legacysupport.timextender.com/hc/en-us/articles/115001313583-How-do-I-move-a-project-from-one-server-to-another

So for History I would choose method 1 as you then export the databases and imports them to Azure SQL using a bacpac export. You don’t need to install anything on a new server, you just need to change the database location from local to Azure and maybe change the authorization method. As long as the data is the same as before it should not complain.

If you want to create new databases, you will have to use some sort of external data transfer to move the history data.

I've managed to now migrate the data with data factory. Just have to exclude the ID and hashed fields and it works perfectly.

Hi @dpjat 

By ID do you mean Primary Key fields, or is it fields similar to hashes that are generated?

How do you then apply these afterwards?

We excluded the DW_Id and some of the automatic hashed fields generated by history tables.

Then on import everything got assigned.

Hi @dpjat did the answers above help answer your question? If so please help us by marking a best answer above. Please let us know if you have any follow up questions