# Copy Dynamics GP data to Azure Data Lake
You can copy Dynamics GP data to Azure Data Lake for future reference after migration to Business Central online. This optional copy gives you access to historical data that isn't migrated to Business Central. It doesn't replace the SQL Server backups used for migration or recovery. See Introduction to Azure Data Lake Storage<https://learn.microsoft.com/azure/storage/blobs/data-lake-storage-introduction>.
To create an Azure Data Lake storage account, sign in to your Azure subscription and create a storage account with Enable hierarchical namespace selected. See Create a storage account to use with Azure Data Lake Storage<https://learn.microsoft.com/azure/storage/blobs/create-data-lake-storage-account>.
In the storage account resource menu, select Security + networking > Access keys > Show keys to get the key required by the Business Central setup guide. Treat the storage account key as a secret. See Manage storage account access keys<https://learn.microsoft.com/azure/storage/common/storage-account-keys-manage>.
## Prerequisites
 You have an Azure Data Lake Storage Gen2 account and access to its name and account key.
 Cloud migration is set up and enabled for Dynamics GP. See Run cloud migration setup for Dynamics GP migration<migration-setup-gp>.
 No other replication run is in progress.
 You have the SUPER permission set to use the Azure Data Lake action on Cloud Migration Management.
## Copy data to Azure Data Lake
1. Sign in to your Business Central online<https://businesscentral.dynamics.com> tenant.
1. Search for and open Cloud Migration Management.
1. Select Azure Data Lake to open the Azure Data Lake Migration Setup guide.
1. Review and accept the warning and privacy notice.
1. Enter Storage Account Name and Storage Account Key, then select Next > Finish.
Monitor progress on Cloud Migration Management.
If you go back to the Azure portal, you can see the data that was copied from your Dynamics GP database to Azure Data Lake. Under the containers section of the Data Lake storage, a new gp-database folder contains the company/system databases, and subfolders contain the series folder and data files.
The database folder in Azure Data Lake is always set to gp-database. If you want to rename it, you can do so after the migration completes. The same applies to the various subfolders. The folders created follow the standard naming convention of the series folders in Dynamics GP. Another folder, 3rd Party, is created, and any files that haven't been mapped to a folder reside in this folder. You can modify the content in the folders after the migration completes.
If an Azure Data Lake migration has already run in the Business Central company, and you launch a second run, the migration tool checks to see if a gp-database folder exists. To copy the data to the same storage account again, you must delete the existing gp-database folder and its contents first.
> WARNING
> Preserve any copied data you need before deleting the folder and its contents.
After the copy completes, you can use the GP data files for historical reference without maintaining the original server.
## Next steps
 Run cloud migration setup<migration-setup-gp>
 migrate-data-replication-run
 Run data upgrade<migration-data-upgrade-gp>
 Complete cloud migration<migration-finish-gp>
## Related information
Dynamics GP migration to Business Central online: End-to-end overview<migrate-gp-overview>
FAQ about migrating to Business Central online from on-premises solutions<faq-migrate-data>

Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/cloud-migration-azure-data-lake-gp, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact. https://jonas-paprotka.de/docs/dev-itpro/administration/cloud-migration-azure-data-lake-gp/
