When a provider finishes an engagement, the website may still depend on their account, notifications, or undocumented configuration. Offboarding should preserve business continuity while removing access that is no longer needed. It begins with understanding the responsibilities being transferred.
List the systems involved
Include the domain, hosting, content platform, analytics, forms, backups, and connected services relevant to the site. Identify the business owner and the provider's role in each. Do not place credentials in a handover document or ask people to share passwords through ordinary email.
Use supported account-transfer and delegated-access controls. Security-sensitive changes should be approved and performed through the appropriate process, with a recovery path where needed.
Confirm the new operator can act
For a hypothetical website care handover, the business may own the hosting account but still rely on the departing provider to restore a backup or update a form destination. Test the new operator's access and instructions before removing the old route.
Check where alerts and renewal notices are sent. A site can keep running temporarily while important warnings continue to reach someone who is no longer responsible for responding.
Close the loop deliberately
Agree which access remains necessary for any final support period and when it should end. Review integrations or tokens separately from human user accounts; removing a person does not always remove a connection they configured.
Preserve approved documentation, source files, and relevant history in the business's chosen location. Follow the agreed retention and deletion rules for copies held elsewhere rather than assuming everything should be deleted immediately.
Start with a short joint checklist covering ownership, access, notifications, and recovery. Offboarding is complete when the business can operate the site and the former provider's remaining access matches the actual agreement, not merely when the final invoice has been paid.

