Migrations are a great opportunity for any site to revise, restructure and clean up it’s content to enhance the user experience, adhere to industry best practices and gain efficiency in content maintainability. We understand that every site has different levels of complexity and functionality and are committed to helping you and your team through this transition and change. During the migration process outlined below, the service will help Site Owners/Administrators understand roles, responsibilities and support offered in the base level, campus funded service. Please see the Terms of Service for specific roles and responsibilities.
We recommend going through the following exercises and processes prior to any type of migration.
Each site is required to establish a Website Owner (please see our Terms of Service for definition). Additionally, the service recommends deciding who your administrative users are, who will have access to add/edit/delete content and who will have access to administer site wide functions before you go live. Roles available to WiscWeb sites are as follows:
For a breakdown of access and abilities associated with each user role in WiscWeb, please reference our KnowledgeBase documentation: WiscWeb - Understanding User Roles
It is imperative that Site Owners communicate with all site administrators and editors about the migration process. This is one of the most important pieces to a successful migration and usually the piece that is thought of last. A few helpful questions to help answer for recipients of these types of communications are:
All users that are responsible for managing content and/or administration tasks on a site are strongly encouraged to review WiscWeb training during the migration process.
Reviewing the training materials provides the following benefits:
**Note: After experiencing issues with user roles, plugins, and site content of migrated sites and our multisite as a whole, we are no longer using the All-in-One Migration plugin to facilitate migrations into our multisite environment.
There are a few options for single site migrations.
Rebuilding the site (most common): This type of migration involves evaluating current site content and rebuilding your site using the UW Theme and it’s predefined page elements. For this, simply request a new site using our New Website Request Form.
This option also has the most benefits to your site and its users:
WordPress to WordPress: The service uses the native WordPress importer plugin for this. If this is an option for you, please see the related KB documentation: WiscWeb - Migrating a WordPress Site into WiscWeb
The WiscWeb Service team has worked with multiple schools, colleges and departments on campus for large migration efforts:
We understand that migration efforts can be stressful for all of those involved and require a great deal of thought and planning; thus, we require a meeting between the service team and the party looking to migrate. In this meeting we will discuss scope, roles and responsibilities, communications, timeline, needed documentation and any constraints either party has. Please send your request to firstname.lastname@example.org.
Please note, this option is cost recovery and the service will provide you with an estimate for time and materials, as well as a Memorandum Of Understanding (MOU) establishing each party’s commitment to the effort. Also, as a cost recovery task, the timeline for this approach is subject to team member availability.
As a reminder, you always have the option to create sites through the normal site creation process, even if there’s multiple.
As a part of the migration process, we highly recommend testing your site with users and stakeholders to make sure everything is functioning as intended and organized in a manner that promotes the best possible user experience. It is the responsibility of the Site Owners, Admins and Editors to ensure the site is ready to launch.
Once the sites are in the WiscWeb system, you will need to follow the “Prepare to Launch” process outlined on the Service’s site.
Please note: we require two weeks' notice for all site launch requests.