![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 25%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EV8%3C/text%3E%3C/svg%3E)
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 43%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
@VJ-8370 - Thanks for reaching out.
- Azure does not support any sort of log analytics migration, even from the backend, such requests are strictly not entertained. However there could be very messy ways to try and get the data over but I'm not sure if it would be worth the effort.
Export the logs from workspace A, to a storage account (or excel), get the data physically downloaded to a machine, from there, either create a custom PowerShell script that would collect the logs, reconstruct them and send them over to the new workspace through the OpInsights REST API. By constructing the logs you're able to also keep the timestamp, although time generated in workspace will still mess things up. However you can still use the reconstructed (e.g. backdated) timestamp and query
the workspace using timestamp and get data in the right order.
Or
- You'd have to do something custom like create a Logic App to read data from the workspace and write to the new one.
Hope this helps.
If the above response helped, Please feel free to "Accept as Answer" so it can be benificial to the community.