Migrate to an AEM Site

The Migration Process section of this page guides you through the steps of a site migration from start to end.

Creating a Site Inventory explains how to develop your own site inventory, and includes a downloadable template for you to fill out.

Creating a Site Map details how to develop a site map, and includes a downloadable site map template to give you an idea of the form and structure of a site map.

Ready to Start an AEM Project? Click here to submit a request.

The Migration Process

After your department has decided to migrate your website to AEM, you will engage in these steps:

  1. Contact the CMS team to plan the migration timeline.

  2. Create a site inventory. This document outlines the titles and URLs of all current site pages (working or not), and which ones will be migrated to AEM. See below for a site inventory template, which you can download and fill out.

  3. If you are re-designing your site:

    • You may wish to conduct a survey or focus group using members of your audience to see how they would map the website. Based on this feedback, you can then build a revised site map to match their expectations.

    • If you do not wish to conduct a survey or focus group, consider the following when building your site map:
      • Who is your audience?
      • What are they normally looking for when they visit your site?
    • Create a site map. This will allow you to determine where the content should go in your new website. See below for a site map template to assist with the production of your site map document.

    • Create a wireframe (i.e., a sketch or blueprint) of your site homepage and content pages on paper.  This will allow you to visualize the content on the page, and helps determine which home page template is most suitable.
  4. Space in AEM will be provisioned for your department to begin site migration.

  5. Groups that are eligible for customized training will have their authors and the Site Administrator participate in a 1.5-hour AEM Authoring Training Session offered by the CMS Team. See AEM Basic Authoring for a list of topics covered in a AEM Authoring Training Session.

  6. Give authors access to the AEM site, migrate site content to AEM. The content migration process essentially consists of copying and pasting content into AEM, and uploading files. This may be done on your own, though many departments choose to hire a Co-op student or a contractor. Site Administrators may ask the CMS team for recommendations on content migrators.

    Tip:  If you are planning to have Co-op students or contractors migrate your content or manage your content on an ongoing basis after the launch, ensure that you have a procedure in place to train new Co-op students/contractors on how to take on the work.  It is also best to have at least one continuing staff member familiarized with the process of updating the site. This is normally the Site Administrator or a lead author.

  7. Inform the CMS team when your site is ready to 'go live', when we will direct your site's URL to point to your AEM site. See Launching an AEM Site for more details.

  8. Add new content to your AEM site, and maintain it to keep the information current.

Website migrations range from several days to several months depending on the scope of the migration. Some SFU sites have fewer than one hundred pages and are moving to AEM, and others may have close to one thousand.

Skilled contractors can typically migrate an average of 3 pages per hour, depending on the complexity of the pages.

Creating a Site Inventory

A site inventory is typically a spreadsheet (eg., an Excel file) that is a list of each of the pages on your site. This is a list of, at minimum, the titles of the pages, URLs, and which pages will and won't be migrated.

A blank site inventory has been provided for you to fill out. The only columns that must be completed are marked in bold. Many departments also assign the page to a contact person in the department. The other columns are optional, but may help in organisation.

* Blank Site Inventory.xlsx
A blank site inventory .xlsx document for you to fill out with your department's website details.

Creating a Site Map

A site map is a document that shows the organization of all the pages on your site. Many are structured similarly to organization hierarchy charts that show the relationship between positions.

The site map template that has been provided below has a few key features. Each of the levels of navigation of the site is represented in its own column. Pages have been spaced out so that authors know exactly which pages belong together, and how they are linked. Background colours have been given to the pages to make grouping clearer, which can be helpful for larger sites.

This site map nests five levels of pages; however, the site can be structured to the level you choose.

Note, larger site maps may take up than one page. For these, it may be beneficial to address one site area or level of child pages at a time. The site map is flexible to your needs - this example is just a starting point.

* Site Map Template.xlsx
An example Site Map .xlsx template.

Developing a Wireframe

A wireframe is a simple diagram that represents the skeletal framework of a webpage or pages. It typically includes the page layout, navigation, and content items. A wireframe usually lacks colour, images and custom typography since the main focus lies in functionality, behaviour, and priority of content. As you begin to develop your site's pages, it can be helpful to sketch out a wireframe of your content areas, particularly for your home page. If you are working with a designer, this document will help them understand what type of content you expect to present on each top-level page.

You can use the following wireframe template PDF to sketch your home page content. Each of the home page templates are available in this document, so you can compare how your content will appear on different templates.

* SFU Responsive Wireframes.pdf
A collection of blank templates of the responsive CLF in desktop, tablet and mobile view.