How did the migration avoid downtime for users?
The migration was staged. The firm’s SharePoint infrastructure was multiple farms running web applications ranging from SharePoint 2010 to SharePoint 2013, so all applications were migrated to a single SharePoint 2016 farm before being transitioned to SharePoint Online. Large sites moved by direct content database migrations between SQL Servers and smaller sites moved with the ShareGate migration tool. The approach produced zero critical outages and 99.9% uptime during cutover, and staff kept access to their collaboration tools throughout.
Did users end up with one login instead of several?
Yes. Users had been logging in multiple times across various platforms, and i3solutions integrated Okta within the Office 365 ecosystem for single sign-on. Logins from three systems were consolidated into one, and Okta SSO with multifactor authentication achieved 95% enrollment across 4,000 users within 60 days.
What were the measurable results?
Zero critical outages and 99.9% uptime during cutover. Password reset tickets fell by 40%, eliminating more than 4,000 annual IT support requests and saving approximately $100K in helpdesk time each year. Retiring outdated infrastructure and licenses saved approximately $300K per year, ongoing maintenance and licensing overhead dropped by about 25%, and the engagement delivered full ROI within the first year.
How is the new SharePoint environment organized?
With Site Collections, Hub Sites, and Office 365 Groups, implemented based on Microsoft’s recommendations. Site Collections organize and manage related sites, Hub Sites restructure the framework of the firm’s web applications so navigation is centralized and connected, and Office 365 Groups support collaboration within designated groups. A custom landing page sits on top of it and lists all relevant projects for each user.
What happened to the older SharePoint sites?
They were retired and archived. i3solutions generated usage reports on the existing environments, identified and categorized sites that were no longer actively used or essential to ongoing operations, and retired those sites rather than moving them. That kept the migration focused on relevant and current data and reduced its complexity.