Select your platform and then browse by platform category

Who are you and what section are you in?

Migrate your previous advanced templates to the Doc Studio

The migration wizard is a feature designed to help customers transition existing advanced (legacy) templates into the new Doc Studio format.

Important

The migration wizard is specifically designed for templates built in the legacy advanced editor. It does not support templates created using the legacy basic (PDF) editor. If you are currently using a basic PDF template, you will need to recreate it within the Doc Studio.


 

Click here for a step-by-step guide
  1. Log in to Employment Hero.
  2. On the left-hand side navigation menu, click on Compliance. 
  3. Click on Template Library.
  4. Locate a template type with Advanced (legacy).
  5. Helpful Hint

    If the template type says Advanced (new), this indicates that it was created by the Doc Studio and does not need to be migrated.

  6. On the template you wish to migrate, click on Actions.
  7. Click on View.
  8. Click on Migrate to new editor
  9. Click on I'm ready, and this will begin the wizard.
  10. The new template will now be cloned. Review and make any necessary edits in the cloned document.
  11. Click on Save.
  12. The original advanced template will remain accessible in your template library. You can access this by clicking on the name of the template, and selecting Advanced (legacy) in the Template Type.

Further information

Can I keep the original advanced templates?
When using the migration wizard, the platform will create a clone of the template in the new editor. This allows you to migrate templates, while keeping the original legacy templates untouched for safe record keeping. You can access the original advanced templates by clicking on the name of the template, and selecting Advanced (legacy) in the Template Type.
Can I still use and assign legacy templates?

You can still view and assign existing templates built using legacy editors to employees during this transition phase.

If you are time-poor, you do not need to migrate all the templates at once. We recommend a phased approach beginning with your most frequently used templates.

What does the "Variable not supported" error mean?

This error appears when the new editor identifies there was a variable in that position of the template, but no variable exists for it in the library. This would most likely happen in instances where users may be manually copying and pasting text. This process does not recreate the variables for them in that instance of the template, so we highlight the variable as not supported because we can't identify what it was.

Resolution: Reselect the variable in the new template if available in the library, or create a custom variable.

Why are secondary and tertiary signature variables not appearing in the variable library?

The secondary and tertiary sending signatory variables will only appear in the variable library if the template has been created with 2–3 sending signatories selected.

Resolution:

  1. Navigate into Template Library
  2. Locate the impacted template and click Actions > Edit Info
  3. Select the desired number of sending signatories
  4. Click Save
  5. Edit the template and search for the sender signatures again in the library
Why is styling and formatting not fully retained after using the migration wizard?

This is expected behaviour and is flagged to users before using the migration wizard. Not all formatting from legacy templates can be perfectly carried over.

Resolution: Fix formatting manually in the new editor. For a detailed response, refer to the support documentation.

Explore related content

Was this article helpful?
0 out of 0 found this helpful