Maintaining Guids for Business Units, Teams and Queues

The Configuration migration tool provides a great way to migrate your configuration data but there are limitations when it comes to be able to selectively filter the records, which makes Business Units in Particular, as well as Teams and Queues will be more challenging to migrate.

The Root Business unit is always different across your instances and there is no way of updating so you have to respect the Root Business unit in the target environment. This can be achieved by updating the references to the Root with the Targets Roots Guid, allowing your dependencies to be chained accordingly.

Exporting records to Excel

You can use the out of the box Export functionality to export your records, Column A of data exported will contain the GUID of the record being exported. The first three columns are normally be hidden when the excel file that is downloaded.

Maintaining record Guid value

Mapping Column A as the primary Key is important step to ensure your relationships and guids are maintained the same across all your environments. Maintaing the same Guids will ensure your references in you workflows and other aretfacts are metadata are preserved during deployments and reducethechance of your deployments breaking. The only guid you cannot control is the root BU which will always be unique.

Changing Order of Rows

Unlike the configuration migration tool that handles the dependencies and relationships, you will be responsible for ensuring the CSV is imported in the correct order so that dependencies are not missed. So you should ensure the records with the most dependencies are imported first by placing them at the top of the CVS.

Also remember to Save as CSV file, and you can include these in your Solution Packages during your deployments as describes in my previous articles.