Decommissioning Area-Specific Intranets

SharePoint 2010 & 2013 migration

SharePoint 2010 and 2013 are now unsupported, increasing the risk of security breaches and data compromise. eHealth Saskatchewan (eHS) has directed that all sites on these platforms be migrated to a supported platform.

This change will affect many intranet sites, including those supporting clinical operations. The following SharePoint 2013 sites are scheduled for immediate migration:

eHealth will migrate content in use to a newer, supported version of SharePoint.

  • All current content associated with the legacy sites (pages, documents, and images) will be moved.
  • The URLs/addresses used to access the content will change, breaking all external links or bookmarks to it.
  • Pages will contain the same information, but the appearance, formatting and navigation will be different.
  • The new URL/address links for the area specific sites will be available via the Area-Specific Intranet Links page. 
  • An SHA network account will still be required to access the content.
  • Current content editor/owners of the SharePoint sites will retain the ability to modify/update content on the new platform.

This migration is an interim security measure in response to vulnerabilities recently discovered on the current platform. Transitioning relevant area-specific intranet content to a provincial system remains a priority. Further updates will be shared as they become available.

Current content owners or administrators of any of the above sites can reach out to SHADigitalHealth@saskhealthauthority.ca for more information.

Frequently Asked Questions and Answers

 

  • Why is this migration happening?

SharePoint 2010 and 2013 are in an unsupported state, creating security vulnerabilities. Migrating the content will ensure system and data security.

  • Will any content be lost? 

All content (pages, documents, and images) of active sites will be migrated. However, saved links and bookmarks to the current sites will break and no longer work. Inactive sites that have not been updated for several years will be archived for three months. This will enable content that is still required to be migrated. Archived content will be deleted after three months.

  • Will content look the same as the original? 

No. Migrated content will remain the same but its appearance, formatting, and navigation will be different on the new platform. 

  • How will I get the new link? 

Updated URLs/links will be available on the SHA intranet on the Area-Specific Intranet Links page once migration is complete. 

  • Will current site editors and administrators keep their rights? 

Yes. Existing editors/owners will keep their permissions to edit their content on the new platform. 

  •  Will this be the new SHA intranet? 

No. This is a temporary step to address SharePoint security issues. A need to review and transition legacy intranet content to a provincial system remains the long-term goal. 

  •  What if I can’t find the content I need?  

Content that is not migrated from legacy platforms will be archived for up to three months, so information will not be lost. If you believe the content is still needed, please connect with your operational leaders to confirm the plan to migrate or transition the content to a provincial platform. 

  •  How can I request updates or changes to the new site when I don’t know who the site owner is?  

Migrated content will continue to be updated according to the procedures associated with the legacy sites (e.g., directly by assigned publishers or by request to the site administrator).  

  •  I have a lot of content to review – can I request an extension on the August 2025 deadline? 

Due to risks associated with the platform vulnerabilities, extensions cannot be granted.  Further review of the content can be done following its migration to the new platform. 

  • I don’t see the Regina intranet listed, is that content being migrated as well?  

No. At this time, only sites on an unsupported version of SharePoint are being migrated. Operational teams using the Regina area intranet are encouraged to start reviewing and identifying the content that will need to transition to a provincial system, once available. 

  • Can I request a separate SharePoint site for my content, instead of having it migrate over with everything else.  

This is not recommended. The current migration is a temporary measure to address security issues. A provincial strategy is needed to coordinate the transition of legacy intranet content to support provincial and area-specific information. Creating standalone sites outside of this process could be counter productive.