Overview
In an effort to ease the transition to using GUIDE 2.0 we have built a self-serve template cloning/migration tool that enables you to clone any of your Legacy templates and have them appear in GUIDE 2.0.
What does “migration” mean and will I lose my template from being available in GUIDE 1.0?
No, you will not lose your original template in 1.0. It will remain and be available to use with Legacy projects. When we use the word “migration” we are really referring to a cloning process and a transformation of the legacy template to a 2.0 format. The legacy template can continue to be used for Legacy projects and the new template can be used for GUIDE 2.0 projects.
How it Works
Navigate to the Templates menu item in the left hand navigation.
If you are seeing the list of Legacy templates, click the banner at the top of the screen to launch the 2.0 experience.
Within the “Projects” tab, navigate to the “Migrate Templates” button in the upper right hand corner and click it.
You will now be viewing a list of your Legacy templates and you can select which templates you would like to clone/migrate by checking the box next to each template.
After you have made your selections, click the “Migrate” button.
You will then see a confirmation modal, where you should read the disclaimer and click “Start Migration”
The screen will then display a green banner letting you know that cloning/migration has commenced and you will see individual status indicators next to each template as it migrates.
Navigate back to the “Projects” tab within templates and see that your template has been cloned over. This template is now ready for use during project creation.
Best Practice: Use cloning as a chance to tidy up your template library. If you haven’t used a template for multiple years, don’t migrate it over to keep your new list of templates free from clutter.
FAQ's
What is the structure of a 2.0 template and how do the pieces get migrated over?
What is the structure of a 2.0 template and how do the pieces get migrated over?
In our Legacy Template we had the structure of Milestones, Task Groups and Tasks. When you migrate over a template that has a Task Group with Tasks contained in it, that gets migrated as a Task with Subtasks. Otherwise Milestones and Tasks get migrated over as Milestones and Tasks.
Why do these get migrated as Project templates?
Why do these get migrated as Project templates?
We are migrating your old “Templates” over as “Project” templates for two reasons. First, is that Project Templates are the unit that can be used during project creation and we wanted to mirror the Legacy experience as much as possible and make it as seamless as possible. Second, the Project Template has the containers for Welcome Messages, which are the landing spots for the migrated Experience Overview language. Once your template is migrated over as a Project Template, you can convert a portion of it to a Phase template if needed.
What elements of templates get migrated over?
What elements of templates get migrated over?
Check out our Release Notes page that has the most up to date version of template elements and what gets migrated.
What do all these different template types mean?
What do all these different template types mean?
Check out our Help Article that discusses our Template Library in depth.