Page 135 - PAM - PROOF
P. 135
V 1.1 February 2024
Part 2: Pre-Migration
In this part of the process you will be provided with a copy of your own migrated
content from your Site Builder site (the data extract). It will come to you as a .zip
file link just as the demo site did. You import the zip file into Local in the same
way as you imported the demo file and use it in the same way.
Part 2 Objectives
The primary objective of this part of the process is to prepare you and your site
for migration to make it run as smoothly as possible and to maximise available
resources. This includes reviewing your migrated site content, planning the
content and visuals of your new SiteWorks site, thinking about how you will
achieve this, practicing using u3a SiteWorks on some of your pages, deciding
whether to continue with migration or opt for a Starter site, and checking or
modifying your Site Builder site for final migration.
Review your migrated site content
Talking to various Web Managers who will be going through this process one of
the questions I am asked about most is about getting data from Site Builder to
SiteWorks and how good the result is.
Regardless of the objectives of this section the first thing you probably want to
do is to take a look at your migrated content to see what it looks like. When you
have your .zip file then open Local, import and select your migrated site file, One-
click admin, and WP Admin, then Visit site to see your pages. If you are reading
this in advance of receiving your .zip file then carry on and you can look at some
of my pages instead.
During 2023 our Development team developed and refined a migration tool that
takes the data from our Site Builder site and imports it to our SiteWorks site. The
conversion tool is not far off perfect. Your photos, file uploads, main pages, sub-
pages, navigation buttons, and more, migrate so there is no need to re-key or re-
upload your information. For me personally I cannot find anything missing* and
that includes all media, all pages, all groups, all contacts, and all events. Others I
have spoken to recently have similar success rates.
* There is one exception. My original Members page has migrated but the
content on it is stored on a separate server and is password protected. I would
not have expected this content to migrate as it is not stored within Site Builder.
The easiest way to explain this is to show you some examples so I shall share
some page screenshots from my own site (desktop display).
Workbook for Web Managers Migrating to u3a SiteWorks Page 135