Move history that supports current work, required access, or justified reporting. Keep the rest accessible through a deliberate archive strategy rather than assuming every old row belongs in the new system.
Prepared with AI assistance. These are practical scoping recommendations; examples are illustrative, not client results.
Identify active dependencies
An old record may still support an open job, a customer question, or a current agreement. Classify history by its operational use, not only its age. Ask the responsible business owners about retention obligations and access needs; those requirements should be established before deciding what to omit.
Compare migration effort
Historical data may use different fields or meanings from current records. Estimate the work required to map it accurately and explain any limitations. Importing everything without context can make new reports less trustworthy. A read-only archive may be more appropriate for records that need occasional reference but no further processing.
Design access to the archive
Staff need a clear way to find older information and understand which system is authoritative. Define who can access the archive and how it is maintained. An archive is not a folder that only the original project owner knows exists. Include retrieval in the operating procedure.
Test an old-record inquiry
Ask a team member to answer a realistic customer question using the proposed new system and archive. Confirm that they can identify the relevant information and its limitations. Use that exercise to decide whether more history should be migrated or whether the archive is sufficient for the actual need.