WordPress Migration & ADA Remediation Project
About the Projects
The WordPress Migration & ADA Remediation Project is a campus-wide effort to move all UWSP websites into a modern, unified WordPress environment while ensuring every page meets current accessibility standards. This work simplifies site management, retires aging platforms like SharePoint and single-site WordPress installs, and creates a more consistent, secure, and sustainable web experience.
In parallel, we’re conducting a comprehensive accessibility review—addressing ADA issues, improving content structure, and providing the tools and training editors need to maintain long-term compliance. Our goal is to ensure all users can access campus information without barriers.
This page offers updates, resources, and guidance on the migration from SharePoint to WordPress, the transition into our centralized multisite, and our continuing accessibility efforts supported by tools like Silktide. It will continue to expand as we add more resources and tutorials in the coming months.
Four Step Migration Process
Step 1
Choose Your Migration Window and Identify What Needs to Move
Start by choosing your migration window (Migration windows listed below) and reviewing your existing content to decide what should move to WordPress. Identify essential pages, update outdated material, and remove anything unnecessary.
Step 2
Schedule a Meeting With Us
Once your timing and content plan are set, schedule a meeting with the web team. We’ll answer questions, map your migration approach, set up your WordPress site, and confirm permissions so you can start building pages and moving content.
Step 3
Begin Moving Content and Building Pages
With your site ready, begin migrating content into WordPress. Rebuild pages, add content, and don’t hesitate to reach out with questions as you go.
Step 4
Use Silktide for ADA Compliance and Perform a Final Content Pass
After building your pages, review your site with Silktide to fix accessibility issues and ensure ADA compliance. Use this time to consolidate pages, remove redundancies, refine content, and confirm everything is accurate, clear, and accessible.
Project Plan and Migration Timelines
SharePoint areas can begin migrating during one of two defined windows. Each window offers different levels of stability, support, and flexibility depending on your team’s readiness. Areas already on WordPress should begin migrating during Window 1.
Window 1: December 8 – Approximately February
During this early window, content will be moved into our test environment while both the multisite and the test environment remain in active development. Because of this, editors should expect to maintain content in two places and encounter occasional bugs, evolving features, and workflow updates. This option is best for teams that want an early start and are comfortable working in a changing environment. All current WordPress sites should start migrating during this window.
Window 2: Approximately February – July 9
This window begins once the test environment is promoted to the live multisite. From this point on, editors will only need to manage content in a single location, and the platform will be far more stable and feature complete. Most departments will find this window offers a smoother, more predictable experience.
Our Recommendation
For the majority of SharePoint areas, we recommend Window 2. It reduces duplication of effort, minimizes disruptions, and aligns better with our IT support capacity. However, the timeline is intentionally flexible, and areas are encouraged to begin migrating in whichever window works best for their schedules and staffing. Our goal is to support your team and keep the process moving without bottlenecks.
Here is the most recent version of the Project Plan. Sites are separated into Winter, Spring, and Summer sections. This is when IT can offer full support if need be and will help prevent our workload from going past capacity. This does not limit when you want to start moving. Once you have a window picked and have met with the web team, you are good to start migrating.
The project plan, as well as the migration windows, are liable to change. We will put our best effort forward to ensure every area can comfortably move to the new WordPress by the end of June 2026.
Web Team open office Hours
Drop In, Ask Questions, and Stay Connected
Our team is now offering open office hours every week to provide hands-on support and direct communication throughout the project. Whether you have quick questions, need feedback on your work, want to share concerns, or simply want to stay in the loop, you’re welcome to stop by.
These sessions are informal and flexible – join for a few minutes or stay the entire time. It’s an easy way to connect with the team, get guidance, and help us ensure we’re meeting your needs as we move forward together.
Schedule for January. Note – Jan 6th and 20th will not be available.
Jan 8th — 2:00pm – 3:30pm
Jan 13th — 2:00pm – 3:30pm
Jan 15th — 2:00pm – 3:30pm
Jan 22nd — 2:00pm – 3:30pm
Jan 27th — 2:00pm – 3:30pm
Jan 29th — 2:00pm – 3:30pm
Frequently Asked Questions
The deadline to move off of SharePoint is July 14, 2026. After July 14, 2026, Microsoft will no longer issue security updates, bug fixes, or technical support for SharePoint 2016, and as such we will not be able to host it publicly anymore.
The most likely reason is that it is a subsite underneath a subsite that is underneath a subsite, or 3 levels deep. Our original intention was for subsites at that level or deeper to migrate alongside their parent site.
If you feel your SharePoint site is separate enough from its parent site, or that we made a mistake on our end, please reach out to ADA-TitleII@uwsp.edu and we will add you to the project plan.
There are two windows in which areas can begin migrating to the WordPress multi-site.
Window 1: December 8th through approximately February
During this period, you would migrate your content into our test environment. The WordPress multisite and the test environment will still be in active development, so you would need to keep content updated in two places. Bugs, evolving functionality, and occasional workflow changes should be expected during this time period. If your site is already on the WordPress single site, please begin migrating during this window. If your site is on SharePoint but you are eager to begin moving, schedule a meeting with us as shown in step 2 above.
Window 2: Approximately February through July 9th
This window begins once the WordPress multi-site test environment is promoted to the live environment. At that point, you’ll only need to maintain content in one place, and the site will be significantly more stable and feature-complete.
Our general recommendation for most SharePoint areas is to wait for Window 2. It provides a smoother experience with fewer complications and better aligns with IT’s workload capacity. The timelines in the project plan reflect when IT can provide full support to each area if needed and help avoid bottlenecks. It is not a rigid timeline and we encourage areas to begin migrating as soon as they can in either window.
Every area can have their own site if they want to. An example url would be www.uwsp.edu/department
Areas can also be housed within a site – for example, all COFAC-related sites might want to be housed under a singular COFAC site. An example URL would be www.uwsp.edu/department/department-related-site.
We’ve added a bug reporting form to the website. When you’re logged in, you’ll see a
blue floating tab on the right side of front-end pages on the website labelled “Report a
Bug”.
Clicking that brings up a form in a modal window. The form has a text box to describe
the bug, will let you attach a file (like a screenshot, if that would help describe the
issue), your name, email, and a checkbox to include information like what page you’re
on, what page you came from, what browser you’re using, and your screen resolution.
Submitting this form automatically creates a ticket in Jira for the web team to take a look
at. This is not the regular IT ticketing system TDX, it is something we use internally in
Application Development.
Due to immense feedback, the timelines given in the Project plan have changed from being a given month to being seasonal. WordPress areas have been assigned Winter, and SharePoint areas have been assigned either Spring or Summer.
These timelines are meant to serve as a general roadmap that helps areas stay on
track and helps IT manage workload capacity. It is not as a rigid deadline, and we encourage areas to begin moving as soon as they can during either Window 1 or Window 2 (check above for info on Migration Windows)
If you are concerned about meeting the July 16, 2026 deadline, please reach out as soon as possible to Noah Warren (nwarren@uwsp.edu), as IT can assist areas in the migration process.
The new WordPress multi-site is not a continuation of the single site and is instead a new site. This had to happen for a multitude of reasons related to scalability, security, and future development.
Many of the features and blocks people grew accustomed to had to be rebuilt from the ground up, and though we tried to make things look the same as possible, there will be differences. Development on these features/blocks is ongoing, so that is why some are still missing. We expect most of the missing features to be added over the next two months.
General guidelines for page counts
While each site functions as its own site, we’re developing broad guidelines to help maintain clear, manageable site structures. These numbers are not final and may evolve as we continue reviewing campus needs.
1–50 pages — Healthy
Your site is in great shape. No action needed.
50–100 pages — Generally Healthy
Your site is still in good standing. Just be mindful of continued growth.
100–150 pages — Needs Review
At this size, it’s helpful to assess content, remove outdated information, consolidate pages where appropriate, and be intentional about creating new ones.
150+ pages — Oversized
Sites above 150 pages may become difficult to maintain and can negatively affect overall site quality. A reduction plan is recommended unless an exception is requested and approved.
These guidelines are meant to support clarity, consistency, and long-term sustainability—not restrict content. Our team is happy to help review your site and discuss what makes the most sense for your area.
You can email Noah Warren (nwarren@uwsp.edu) or Dawn Anthes (danthes@uwsp.edu) your question, or you can virtually stop into the Web team open office hours (link and times are listed above) to ask your question(s).
Need additional Help?
If you have questions about the WordPress migration project, ADA remediation, or improving your department’s web content, please reach out to ADA-TitleII@uwsp.edu or nwarren@uwsp.edu. We’re here to support you.