Microsoft Dynamics 365 migration to ServiceNow

[Urvershi Anand]

Hi Everyone,

Has anyone worked on the migration from Microsoft Dynamics 365 to ServiceNow, would really need some help for the process of attachment migration from MS Dynamics 365 to ServiceNow.

Thanks in advance!!

[Andrewa54814525]

Hi Urvershi,

Yes, this scenario does come up, especially when organizations move specific workflows from Microsoft Dynamics 365 to ServiceNow.

Attachment migration is usually one of the trickier parts, not just because of volume, but because of how files are stored and linked in Dynamics.

In Dynamics 365, attachments are typically stored either in Azure Blob storage or within the database, and they are linked to records using notes (annotations) or document management. ServiceNow stores attachments differently, linking them through its own attachment structure.

A few things that usually help in real projects:

First, confirm where your attachments are stored (Azure Blob, database, or SharePoint). This affects how you extract them.

Make sure you extract metadata along with the files. You’ll need record IDs, entity names, and timestamps to correctly reattach files in ServiceNow.

Maintain a clear mapping between Dynamics record IDs (GUIDs) and ServiceNow record sys_ids. Without this, attachments won’t link properly after migration.

If you’re dealing with large volumes, process the migration in batches instead of all at once to avoid performance issues.

In a few implementations I’ve seen, including work handled by teams like Dynamic Netsoft Technologies, the biggest challenge wasn’t moving the files but making sure they stayed correctly linked to the right records after migration.

If you’re still early in the process, try a small pilot migration first. It helps identify issues before doing a full-scale move.

If you can share how your attachments are currently stored, I can suggest a more specific approach.