During the 2018-2019 academic year, the Stanford Sites Cloud Migration team — consisting of Stanford Web Services (SWS) and University IT’s (UIT’s) Administrative Systems teams — are moving approximately 2,400 Stanford Sites websites to the cloud.
During the first phase, the Stanford Sites Cloud Migration Team moved group and department websites, followed by individual faculty, student and staff websites. In the current phase — happening now through the end of February 2019 — websites using the Stanford Sites Jumpstart service and those custom-built by Stanford Web Services will be migrated.
Why is this happening?
We are committed to ensuring your Stanford Sites website is easy to use, performs well, and is readily available when you need it. Moving websites into the cloud offers a better experience both for you as the website owner, and for website visitors. This includes faster loading time, integration with Stanford IAM (Identity and Access Management) infrastructure (SAML 2.0), and on-demand scalability and availability. Learn about the benefits of moving to the cloud.
How does it affect you?
Your content will be the same, and you will not lose any permissions.
Editing during the migration
During the migration of your website — which will occur between 6:00 p.m. and 11:00 p.m. on your designated migration date — you should not make any changes or edits to your site. You will receive an email reminder so you and other website editors can plan accordingly.
How does it affect visitors to your site?
Your website will be offline for a period of up to 30 minutes between 6:00 p.m. and 11:00 p.m. on the date of your migration. Visitors will see a message that the site is offline for maintenance.
Steps to take before your website is migrated
First, you will receive an email confirming the website(s) that will be migrated and when. You’ll also receive a reminder email several days prior to your migration. Before your website is migrated, please take the following actions:
- Inform website editors/contributors about the migration. Let them know that the website will be unavailable for editing on the specified date and times, so they can plan accordingly.
- If a website is no longer in use, we don’t need to move it to the cloud. To delete the website and opt out of the migration altogether, complete this form.
- To transfer ownership of a website, please submit a Help ticket.
- If any of your websites contain High Risk Data, or you do not want them to be in a shared hosting environment for any other reason, please submit a Help ticket.
If you do not take any action, we will proceed with migrating your website to the cloud.
During and after migration
It is important to avoid making any edits or changes to your website during the migration. Any changes made during this time will be lost.
We will make several efforts to make this process as seamless as possible for you:
- You will receive an email several days before the migration, as a reminder to hold off on making website edits. If edits are made by mistake during the migration, please let us know so we can resolve this issue as soon as possible.
- Migration is expected to be completed in one evening, between 6:00 p.m. and 11:00 p.m.
- While we do not anticipate any issues to arise due to the cloud migration, we will retain a backup copy of the websites offline as a precautionary measure.
- We will email you when your website is officially in the cloud, and you will then be able to return to making edits.
What about development websites?
If you have a development environment of your Stanford Sites website, it will be retired one week after your production website migrates to the cloud. If you're not sure if you have a development website, please let us know.
If you have questions or feedback about the Stanford Sites cloud migration, please let us know.