web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / CRM huge attachments size
Microsoft Dynamics CRM (Archived)

CRM huge attachments size

(0) ShareShare
ReportReport
Posted on by Mohammad Yusuf 71

Dear All,

We are migrating crm 2013 to crm 2016 onpremise.We have huge attachments .Annotation table  size is 245 GB.

Org DB size us 350 GB.

we want to keep the attachments as is.

What will be best approaches while migrating using Organization import approach?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Dynamics Objects 365 Profile Picture
    Dynamics Objects 365 550 on at

    According to me, best approach to save the Storage would be to move the Attachments to Azure Blob or Sharepoint.

    Add a link to that file on storage location to the actual CRM record.

  • Suggested answer
    Kokulan Profile Picture
    Kokulan 18,054 on at

    Hi

    You are right, you will save a lot of time, if you do the Organization Import as your attachment data does not have to be migrated.

    Any other approach will be a lot of time consuming, considering the size your DB file

  • Verified answer
    David Jennaway Profile Picture
    David Jennaway 14,065 on at

    If you're doing an organisation import, then I don't think the size of the attachment table will have much impact on the time it takes, as it won't need to process the data in any way. It would affect the time to copy or backup/restore the database, but that's not normally a large part of the overall upgrade time

  • Mohammad Yusuf Profile Picture
    Mohammad Yusuf 71 on at

    Thanks David

    To make the import fast we are thinking of below approach please guide us.

    1. Restore the Org DB on sql server 2014.

    2. Take a backup of Annotation table in a new custom DB.

    3.Set the documentbody column of Annotation table to Null.

    4.Shrink the Org DB to reclaim the attached files space.

    5.Import the Org

    6. Update the documentbody from Backup table

    Is this approach right?

  • Suggested answer
    prt33k Profile Picture
    prt33k 6,907 on at

    The approach will work but it is unsupported.

    If it is onprem then simply import the org - 300 GB isn't that big that import wont handle. You can always involve support team in case you get error. But with direct CRM table manipulation even the support team wont be able to help since you went the unsupported way.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans