Sunsetting

What Is Sunsetting?

Sunsetting is the planned, staged phase-out of an application or system. Sunsetting means users are told what is happening, when, and what to use instead, rather than finding out when the login page stops loading.

It usually runs in stages. The retirement is announced. New use is restricted, so no new records or accounts are created. A data freeze stops transactions. The system may move to read-only for a period while users finish remaining work and confirm they can find what they need in the archive. Then it is retired.

Sunsetting is the part of retirement that users see. The technical teardown, including extraction, archiving, and infrastructure removal, happens behind it. A retirement can be technically flawless and still fail if nobody told the people who relied on the system.

Key Points

• It is staged, not abrupt. Announcement, restriction, freeze, read-only, and retirement each give users a chance to adjust.
• Notice is the core deliverable. Users and dependent teams need enough lead time to move workflows and integrations.
• New use stops first. Blocking new records early keeps the volume of data to archive from growing.
• Users need an alternative. Either a replacement application or access to the archive, confirmed before the switch-off.
• It precedes the technical teardown. Sunsetting handles the people side. Decommissioning handles the systems and data.

Common Use Cases

Retiring an internal application

A business unit’s custom application is replaced by a corporate platform. The team announces the schedule, blocks new entries, and moves users to the archive for historical lookups.

Vendor product sunset

A vendor announces it will discontinue a product. Customers use the notice period to export data and archive it before access ends.

Winding down a legacy platform

A long-running platform is switched to read-only for a defined period so users can verify they can retrieve everything they need before final shutdown.

Sunsetting vs. Related Concepts

Retirement vocabulary overlaps heavily. Here is how the pieces divide.

SUNSET DATE

The specific date on which the application goes offline. Sunsetting is the whole process leading up to it.

APPLICATION RETIREMENT

The full lifecycle end: archiving the data, transitioning users, and shutting down the infrastructure. Sunsetting is the user-facing phase within it.

END-OF-LIFE (EOL)

The vendor’s declaration that a product is done. Sunsetting can be a response to EOL, or an internal decision that has nothing to do with the vendor.