When you retire a product, plan the data, domains, credentials and infrastructure as carefully as the announcement. Notify users, give them a way to export data, delete or retain data on a documented schedule, release the keys and accounts, and remove the servers. A half retired service is an easy target.
Before announcing
- Inventory everything the product touches: servers, databases, storage, domains, certificates, queues, scheduled jobs, third party accounts, and service accounts.
- Find the dependencies in both directions. What does it call, and what calls it? Other teams may rely on an endpoint without anyone remembering.
- Decide the data fate: delete, archive, or hand over. Check legal retention rules, contract obligations and privacy requests. Ask your legal advisor, as rules vary.
Communicate and give users an exit
- Announce with dates, in plain language, through the channels users already receive.
- Provide data export in a usable format, and test it.
- Say what happens to their data and when it is deleted.
- Warn that old API keys, webhooks and integrations will stop working, with the exact date.
During wind down
- Stop new sign ups first, then new data, then logins, in stages.
- Keep security patches flowing until the last day. An unmaintained internet facing service is a liability.
- Keep monitoring on. Wind downs invite confusion, and attackers like confusion.
- Watch for phishing that uses the shutdown as bait. Tell users how real messages from you will look.
Shut down and clean up
- Take a final backup if required, and store it encrypted with a documented deletion date.
- Revoke API keys, tokens and service accounts, in the product and in third party services.
- Delete or archive data as promised, and record the deletion.
- Remove DNS records, or point them somewhere safe. Dangling records to deleted resources can be taken over by someone else.
- Keep the domain registered. Letting it lapse lets others claim it and receive mail and traffic meant for you.
- Terminate servers, volumes, snapshots and monitoring agents. Snapshots and old backups are the usual forgotten leftovers.
- Cancel vendor subscriptions and close their access.
- Update asset inventory and compliance documents to reflect the change.
Keep the record
Store the deletion confirmation, the date of each step and who did it. Customers and auditors may ask later.
Asset discovery in Safeguard can help find the forgotten pieces, though a careful inventory by hand works.
Assign one owner for the shutdown with a written plan and dates. Wind downs fail when everyone assumes someone else deleted the last server. A simple tracker with each item, an owner, and the evidence of completion works well. Review the tracker after ninety days, and look for new traffic to old addresses, which can signal forgotten dependencies.
Quick check
Should we delete everything immediately?
Not necessarily. Retention duties and user export windows come first. Delete on a documented schedule.
Why keep the domain?
An abandoned domain can be registered by someone else, who may receive your old users' email and traffic.
Last reviewed: 19 October 2026.
