Pre-Migration Checklist

When a u3a (or Network/Region) with a Site Builder site joins the SiteWorks programme and the Web Manager has been trained, they will be allocated a member of the Migration team. At this stage they will have the opportunity to take an export from Site Builder to help assess how to proceed.

These points and actions will ensure that the Site Builder site migration goes as smoothly
as possible and minimises the editing required to finalise the initial SiteWorks website..

General Planning

Before undertaking any migration process, the Web Manager (site content creation and maintenance), together with their Committee, should undertake a critical review of the current site and ask a number of fundamental questions as to the purpose, scope and contents of the website.

  • Consider how the design of the new site, reflects the u3a going forward. Some features in Site Builder (e.g., sidebars and scrolling banner), are not available in WordPress and SiteWorks but have equivalents.

  • A website is not a document repository, hence review the material that will be migrated, for example how much of the newsletters and meeting archives actually needs to be transferred.

  • If the committee would like to change the u3a name part of the URL this should be discussed.. For example, if your u3a is ”Blueberry and District” and your Site Builder URL is then rather than it could be just be when hosted on SiteWorks.

Migration Limitations

Note the following points:

  • Site Builder Colour scheme, Banner Message, Links to Google Calendar and YouTube Videos are not migrated.

  • The Gallery page is not migrated, but all media elements will be.

  • Text marked as a centred heading in Site Builder { … } is converted to a HTML level 3 heading in SiteWorks. Headings are automatically rendered in bold font. If in Site Buiilder you use the bold markup # … # in combination with the { … } heading markup, the heading text will be rendered in ”bold bold” in the new site which can look rather ugly.
    This can be corrected either in Site Builder before migration or in your new site after migration. The use of the Site Builder bold markup # … # in regular text causes no issues.

  • The ampersand, &, is a reserved character within the code used to migrate sites, hence can cause problems both for exporting data from Site Builder and for importing it into WordPress. The migration process is more reliable when ampersands are avoided. Consider replacing the & symbol with ’and’ within a page or group names.


The checklist details specific task or points to note. The order is that of the Site Builder main menu.
It is recommended that this document is printed, and each item tick off during the checking process.

Check the u3a Site Profile (under Utilities), to ensure that there are no unmatched links. If a link is unmatched, it should be corrected or removed by editing the relevant page.


Use the Site Builder Groups menu to review your groups and remove any that do not required migration to the new site. If a group is marked with a status of ’Hide’ it will be migrated and given a publication status of ’draft’ in SiteWorks.

Check the contents of any in-line emails contacts, to ensure they are required.


Remove any Events that you don’t want migrated, but if an event’s details are used as a template for future meetings, temporarily reset the date to somewhere in the future if required so that it will be migrated.

Ensure that the first line of the event details in Site Builder contains only the title of the event.


Edit or remove any contact, as required.


From the Links menu, edit or remove any invalid or unused links.

Remove any non-u3a logos with links as these will not migrated.

Ensure any email set to ’in-line only’ should either be removed or set to not in-line only.


Edit or remove any pages, as required.

If a page has little or no text, the page should be removed.

Ensure that pages do not contain visible email addresses unless it is the intention that they should be shown publicly and that doing so does not contravene the provisions of the GDPR.

Check that any URLs in the text are correct.

Inline links (i.e. those using | name of page or document |) should be checked to ensure they link to the intended target page.


Check the Pictures menu to ensure that links to missing pictures are either removed (using the Remove links to missing pictures option), or the picture is uploaded, if required.


Check the Files menu ensure that links to missing files are either removed (using Remove links to missing files), or the file is uploaded.

Password protected files, will not migrate unless protection is removed.