The Project module in Business Central is highly versatile and often serves as a core component of operations for the industries that adopt it. It becomes embedded in day-to-day processes, with many users spending a significant portion of their time working within it. However, the Project module has a notable limitation: the inability to effectively segregate completed data from in‑progress data. There is no robust mechanism to manage the ever-growing list of projects once ledger entries have been posted to them, and the system simply relies on the “Completed” status for historical projects, which remain in the same table indefinitely. This is unnecessary and performance‑draining. As a result, the list of projects that users must navigate continues to grow, making it increasingly difficult to locate relevant records. Filtering can be applied, but as the underlying dataset expands, performance degrades and the experience becomes more cumbersome. Compounding this issue, all records reside in the same table, so integrations using web services to access and export project data can encounter performance and scalability challenges due to the volume of records involved.

The introduction of Project Archives provided the ability to track and retain the history of project revisions and to restore projects to a prior state if required. This functionality should be extended to support the closure and removal of fully completed projects that have no ledger entries in the current open period. Enabling this would reduce the volume of active data that users must work through and help ensure that the Project module remains responsive. At the same time, it would preserve the historical information organizations may need by relocating it from a heavily used operational table to a dedicated archival table.