This project is read-only.

Please follow the steps below to use this tool.

  1. Go to Downloads section of the page, download the file, unzip and save it to a location of your choice.
  2. In the unzipped folder, double click the file ‘AccessTemplateMigrator.exe’ to launch the application. You should see a screenshot similar to the one below.


  • Connect to both you Source and Target CRM instance. Once you connect the first time, you will have an option to store your credentials for future use.



  • In the form you have two sections – “Select Templates to Migrate” and “Update Template Reference in solution”. First I will explain the top section. Click on the ‘Load Templates’ icon on the top bar. The system would populate all the access team templates available in the source organization and show it in a TreeView.


  • Select the access team templates you want to move to the target environment and then click on Migrate icon. Please note a very important point here. The utility would determine the condition of update or create of the template based on the following condition
    • the utility would first check for any templates in the target organization based on the name of the template and entity for which the access template is created. If a match is found then it would be retrieved and updated with the latest values from the source organization
    • If a match is not found, then the access template would be created in the target environment.
    • If there are two access templates with the same name for the same entity in the target organization (I am assuming under what scenario it would be required or you would do it), this tool will take the first of the duplicates and modify it with the source values. So results sometimes will not be as expected.
  • While the migrate is happening the tool will take care of the fact that if the entity in the target environment is not enabled for access team template creation, the utility would update the entity metadata to enable creation of access teams in the target environment for that entity.
    • However one very important caveat to note here is that, the utility assumes that the entity is present in the target environment. If not present, it would throw an error. Future versions of the tool will handle this caveat.


  • Now the templates are updated in the target environment. However access team template id’s are different across environments. And if you have configured your access team grid for  any entity, your solution’s customizaton.xml file would contain reference to the access team template. Check for the screenshot below where my solution contains an access team grid configured on the entity form.


These guids needs to be updated with the Guids of the access templates in the target environment. Let’s see how this is achieved by the utility.

  • On the top bar, you would find an icon called ‘Download Template Xml’. Click on the icon and you would be prompted to save a .xml file.


  • Save the xml file to a location of your choice. Now coming to the bottom section of the tool
    • select the Source CRM solution which contains all your customization and you would move to the target environment.
    • In ‘Select Template Xml’ section, select the xml file that you saved in previous step.
  • Click on the ‘Update Template Reference’ image icon. The utility would update all the template references of present in the solution with the appropriate Id’s from the target environment and once completed you would be presented with a dialog to save the updated solution.


  • Save the solution to a location of your choice. Your solution is now ready to be imported to the target environment. Once you import this solution in the target environment, you would find that whatever form customizations you did for the access team grid set-up on entities in the source environment, is working as expected in the target environment as well.


Hope you would like this tool. In case of any issues, please e-mail to and I will get back to you.

Last edited Nov 2, 2015 at 2:19 PM by debajdu, version 3