Dynamics Community Forum Thread Details

Converting and Loading Dynamics CRM On-Premise Customization Files Into Dynamics 365 for Sales

Been asked if we can load some "older" on-premise Microsoft CRM customization files (i.e. ZIP with xml config files) into a few Sandbox environments.

Tried using the Import Solution feature error raised.

"The solution file is invalid. The compressed file must contain the following files at its root: solution.xml, customizations.xml, and [Content_Types].xml. Customization files exported from previous versions of Microsoft Dynamics 365 are not supported.

Given the dates on some of them, we're not surprised their no longer compatible. Wondering if anyone can suggest any details, tools or otherwise to help convert "old" to "new" format - if exist?

Alternatively, we may looking to manually recreate one entity/table at a time (not ideal).

Thank you in advance for your suggestions.

Michael

Dealing with older on-premise CRM customization files can be challenging, as the formats have evolved, and compatibility issues are common. Here are some options you could consider to convert or update these solutions, along with details on available tools:

1. Use the Solution Packager Tool

Microsoft’s Solution Packager tool, part of the Dynamics 365 SDK, can help by unpacking the old solution zip file into separate XML files.

Once unpacked, you can examine and edit the XML files to align with newer Dynamics 365 formats.

After making necessary adjustments, you can repack the solution using Solution Packager and attempt re-importing.

Steps:

1. Unpack the old solution using Solution Packager.

2. Identify outdated schema or unsupported components (e.g., outdated attributes, entities, etc.).

3. Modify these components to be compatible with Dynamics 365.

4. Repack and test in a sandbox environment.

2. Use Configuration Migration Tool

If your primary goal is to migrate data structure (e.g., entities, fields, and relationships), the Configuration Migration Tool can help export and import configuration data.

This is useful for extracting entities and their metadata, which you can then recreate manually in the new environment.

Note: This doesn’t cover the entire solution but helps with the basic structure.

3. Manual Recreation in New Environment

While this isn’t ideal, recreating the components manually is sometimes the cleanest option for highly outdated solutions.

Using your unpacked files as a reference, you can rebuild one entity, view, form, or workflow at a time, ensuring compatibility with the new system.

You could create a PowerShell or script to automate aspects of the XML processing to speed up the transfer of repetitive elements like fields and relationships.

4. Third-Party Tools

Tools such as XrmToolBox plugins might assist in parts of this process, especially for entity structure migration or customization management.

The "Solution History" plugin within XrmToolBox might provide insights on older versions, though it’s more useful for organization than direct conversion.

Points to be noted:

Schema Changes: Some CRM components, like attributes and relationships, may have structural differences in the XML that need manual updates.

Deprecated Features: Old versions might contain deprecated features that won’t be supported (e.g., legacy workflows or custom script methods). You’ll need to reimplement these in supported formats.

Testing: After converting, thoroughly test in a sandbox to ensure functionality before moving to production.

Each method has trade-offs, but using the Solution Packager to modernize the XML structure tends to be a good first step before considering a manual rebuild. Let me know if you’d like more specific steps on any part of this process.

Quick Links

Subscribe to this forum!