It is the most common use case. For example, a company changes the financial software because of an acquisition. According to the regulations, they still have to keep its data for a few years.

It's historical data that won't change anymore, however, occasionally it has to be accessible to end users as a reference, also for auditors.

For this use case, the natural choice for backend and user interface is an archiving solution. It usually provides a wizard to configure a search application GUI and implements the archive administration workflow (user roles, retention policy, etc).

However, the archiving system requires data packages with aggregated records, which is a challenge.