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) / Deleting Fields prior ...
Microsoft Dynamics CRM (Archived)

Deleting Fields prior to re-import of Organization

(0) ShareShare
ReportReport
Posted on by Tonya Welch 25

Hello everyone.  I am currently working a migration from CRM 4.0 to CRM 2011.  I inherited this system and the developer before me used a lot of unsupported code/methods to add functionality to the system.  I'd like our CRM 2011 deployment to be fully-supported.

Toward that goal, I have created a CRM 2011 sandbox and imported the database from the CRM 4 production system and now I am currently re-writing all of the code to update to Xrm and to find other ways to achieve the functionality that is done via unsupported methods.  As part of this process I am deleting a lot of unused fields for general clean-up.  When I have this complete and we are ready to fully migrate, I plan to export the modified solution, import the latest version of the production 4.0 database, import the organization from that database, then import my modified solutions.

My question is this:  Will all of these fields I'm deleting have to be deleted again, since the imported database tables still have columns for those fields?  Does importing a solution delete fields that are in the database, but not in the new solution?

Thanks everyone.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Bryan Botz Profile Picture
    Bryan Botz 600 on at

    Hello Tonya,

    If I'm understanding your process correctly if you are deleting the fields in the UI it should flag them and that will carry over when you import the database to CRM 2011 and it goes through the upgrade process. That is if you are doing this in the org with the database you intend to import. If you are just doing this on a test server and hope to apply the new solution, those old items will carry over when imported.

    Depending on how much data is present if you are concerned about a variety of unsupported modifications you might consider exporting the data such as by CSV files and them importing them to a clean environment. That might take more work again I'm not familiar with the variables of your data and deployment. To get more assistance with the logistics of this you might want to consider working with one of our partners and they can help consult a few different methods to approach this. If you encounter errors after the import please feel free to contact us at technical support and we would be happy to assist you further.

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 March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
JS-09031509-0 Profile Picture

JS-09031509-0 3

#2
AS-17030037-0 Profile Picture

AS-17030037-0 2

#2
Mark Eckert Profile Picture

Mark Eckert 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans