Skip to main content
Skip table of contents

Migrating Templates from the Classic to the NextGen App

The Classic and NextGen templates are not compatible. This article explains how to create new templates from the original Classic templates to use in the NextGen app.

NextGen templates can be used in the Classic App but Classic templates cannot be used in the NextGen app.

The primary distinction between Classic and NextGen templates lies in the handling of dynamic data. Classic templates use Bookmarks, whereas NextGen templates use MergeFields and DocVariables. This variance renders Classic and NextGen templates incompatible.

If you are planning to use your existing templates from Classic, it is required to replace the bookmarks in the files before they can be used in NextGen. We will refer to this process as ‘Migrating templates from the Classic to the NextGen App’.

Before you start migrating templates from the Classic to the NextGen App, make sure you are familiar with Creating a template from a Word File.

The article is based on Microsoft 365 version of Word. Please note that the user interface may vary depending on the version of Word you are using.

Video Tutorials Available

You can find video tutorials with real examples explaining the template migration process in the Templates Tutorials article.

Let’s start…

  1. Using Microsoft Word, open the template (*.dot or *.dotx files) that you want to migrate.

    image-20240402-043023.png

  2. In the Classic templates, dynamic data is added by inserting bookmarks as FORMTEXT. You'll need to replace each FORMTEXT with the new elements used by the NextGen app.

    If you cannot see the FORMTEXT area or find it difficult to locate where FORMTEXT is being used within the document, press Alt + F9 to show/hide the FORMTEXT fields.

    image-20240404-023814.png

  3. To see what each bookmark is for, double-click or right-click on each FORMTEXT and then click on Properties, the Text Form Field Options window will open. In the Bookmark field on the Field settings section, you can see the reference of the bookmark. Take note of the bookmark as you need to replace this element.

    image-20240402-043359.png
  4. Before replacing the FORMTEXT Fields, you need to know the name of the new bookmark. The easiest way to do so is to download the list of bookmarks: Download Bookmarks for Word Templates.

Tip

You can easily find the corresponding new bookmark for replacing each FORMTEXT field by referring to the eBECAS/EDMISS Template Bookmark Dictionaries. Download the dictionary spreadsheet to locate the desired Classic Template Bookmark and its corresponding Next Generation Template Bookmark.

  1. From the bookmarks list, find the bookmark you want to replace, highlight it and copy it.
    For example, locate the bookmark for "Student Name," then highlight & copy it.

    image-20240801-015836.png

  2. Go back to the Word document and paste the copied bookmark replacing the FORMTEXT field.

    image-20240801-020100.png

  3. To replace the FORMTEXT fields used in the grids or tables, there are 2 options:

    1. Grids in Tables (recommended): Convert it to a Grid in a Table in the current word template. This is the easiest and recommended way to migrate a grid.
      See this article for detailed instruction: Insert a Grids in Tables

    2. Grid Templates: An alternative is to create a Grid Template that can be reused in other templates like modules, and insert it as a DocVariable. This is a more flexible but also a more complex way to do it so it is only recommended if you are familiar with templates.
      See this article for detailed instructions: Creating Grid Template and Creating a Template in Microsoft Word | Insert Grid Templates or Section Templates

image-20240801-020453.png
  1. After updating all the fields, save the template as .doc or .docx format.

  2. Upload the word file through eBECAS/EDMISS NextGen Templates.
    See the following article for detailed instruction: Creating a Template from a Word File | Upload a Microsoft Word Template.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.