Best Practices for Decommissioning a SharePoint 2013 Farm
Question details
The user needs a structured guide to safely retire a legacy SharePoint 2013 farm after migrating data to SharePoint Online.

- Product
- SharePoint 2013
- Device & OS
- not provided
- Scenario
- Decommissioning legacy servers and farm environments post-migration to SharePoint Online.
- Observed behavior
- A planned sequence is required to preserve dependencies, custom solutions, and compliance records, ensuring no unexpected failures occur during the server removal process.
Ensure that all user traffic has been successfully redirected to SharePoint Online and that a complete, verified backup of your SharePoint 2013 farm and SQL databases is safely stored off-site.
Step-by-Step Guide to Safely Decommission a SharePoint 2013 Farm
Follow this structured sequence to document, validate, and systematically shut down farm components to avoid data loss and unseen dependency failures.
Decommissioning a SharePoint farm is a delicate process that extends beyond simply powering down servers. It requires a thorough audit of dependencies to ensure external systems do not fail once the farm is offline.
Confirm that all essential data, site collections, and compliance records have been successfully migrated to SharePoint Online. Double-check your organization's data retention policies to ensure no legacy data is prematurely destroyed.
Perform a comprehensive audit of the farm to identify active custom applications, third-party integrations, hardcoded DNS records, SSL certificates, service accounts, and scheduled jobs that still point to the legacy environment.
Before fully dismantling the environment, lock the SharePoint 2013 farm into a read-only state. This prevents users from adding new content to the old system and acts as a grace period to monitor for any broken links or lingering integrations.
Begin stopping or removing farm components in a planned sequence. Start by taking the Web Front-End (WFE) and unused application servers offline. Monitor network traffic to verify no active service requests are being dropped.
Only after all web and application dependencies are confirmed to be completely inactive should you proceed to decommission the backend SQL database servers and remaining underlying infrastructure.
Manage Your Migration Documentation with WPS Office
While decommissioning complex environments like SharePoint requires careful IT planning, managing your migration checklists, server inventories, and project timelines doesn't have to be complicated. WPS Office provides a free, lightweight, and highly compatible suite to handle all your IT project documentation.
- 1. Download and Install: Download WPS Office Free and install it on your IT admin workstation.
- 2. Create Server Inventories: Open WPS Spreadsheet to build detailed checklists mapping out all your web, application, and database servers.
- 3. Share with Your Team: Save your migration and decommissioning logs in standard .xlsx or .docx formats to collaborate with the rest of your IT department seamlessly.

Frequently Asked Questions
Should I delete the SharePoint 2013 SQL databases immediately after server shutdown?
No. It is highly recommended to keep the SQL databases intact and backed up for a designated retention period after decommissioning the SharePoint servers, just in case unmigrated legacy data is suddenly required.
How do I handle custom solutions (WSPs) during decommissioning?
Custom WSP solutions cannot be directly migrated to SharePoint Online. You must audit what these solutions do, recreate their functionality using modern alternatives like Power Automate or SharePoint Framework (SPFx) in the cloud, and safely disable them on the 2013 farm before taking it offline.
Can I just turn off the virtual machines to decommission the farm?
Simply turning off VMs without a proper inventory can break external dependencies, scheduled tasks, custom DNS routing, or integrated third-party applications. Always audit the environment and cleanly disconnect services before powering down the servers.




