Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This article documents the process for importing the Business Process Catalog with the March 2026 or newer releases. If you want to use older versions, please refer to Import the Business Process Catalog using a Power Automate flow.
This article describes how to import Microsoft's business process catalog into Mavim using the MTDX database file available on the Microsoft Download Center. Mavim is a business process management platform that you can find in the Microsoft Marketplace.
Before you import
Before you import the catalog to the Mavim platform, there are a few things that you must do and consider. Ensure that you're ready to import the catalog with the following list.
Download the process catalog
Download the latest version of the catalog from https://aka.ms/BusinessProcessCatalog. Make sure you download the Mavim Database (.MTDX file) version of the catalog.
Important
The December 2025 release and newer versions of the Business Process Catalog included all new Fieldsets. Therefore you must uncouple the Fieldsets in your Mavim environment from the topic types that were used in the previous releases of the business process catalog. To do this follow these instructions.
Uncouple field sets
- Open Mavim Manager.
- Select the Administration tab in the Action Pane.
- Click on Administration Topic Types.
- In the Topic Types pane, select the types from the list one at a time.
- Process
- Task
- Module
- Primary Topic
- Meaning
- In the Assigned Fieldsets pane, select each of the following fieldsets, and then click Remove. You can select and remove multiple assigned fieldsets at the same time by holding Shift on your keyboard. This process may take several minutes for each topic type.
- Dynamics 365 Process attributes
- Dynamics 365 Fit Gap
- Azure DevOps
- Dynamics 365 Process stage
- Dynamics 365 Process modifiers
- Dynamics 365 User Story
Import the Database
Use the following steps to import the MTDX file into your Mavim environment.
- Open Mavim Manager.
- Select the Database where you want to import the latest version.
- Click the Action Toolbar in the virtual machine.
- Click File Transfer > Upload.
- Select the .MTDX file you downloaded from the Microsoft Download Center.
- Wait for the database file to upload into the virtual machine.
- When the import is complete, click the Modelling tab in the Action Pane.
- Click Import > Version.
- Select the .MTDX file you just uploaded. The uploaded file is stored in the TempDisk drive by default. You can find this by clicking on This PC.\
- Select the file and then click Open.
Note
The Mavim version with the business process catalog is now loaded into your purple cabinet called "Imported Versions". Be aware that it can take several minutes to complete this action.
After you import
To be able to start working with this process model, you need to copy it to your yellow cabinet. If you want the full experience, it's important to copy the entire structure (including the External References part) to your yellow cabinet. The easiest way is to right-click on the purple "Business Process Catalog Export …" topic you imported and click Copy. Then expand your yellow cabinet node and paste it anywhere you like (ideally somewhere near the root, for example directly under the "Relationship Categories" topic.
Again, this copy and paste action might take several minutes to complete. Once finished you have the latest version of the BPC available in your Mavim environment. You can either directly create a new version definition that includes this structure and create a version and publish that version to your Mavim portal to explore it. You can also make some adjustments like adding additional fields or processes.
Next steps
Follow the process-focused approach of the Success by Design methodology when implementing Dynamics 365
Manage the fit-gap analysis in Mavim and synchronize your enriched business process catalog to Azure DevOps.