Enterprise Archive or Active DMS: Where Do Records Belong?

Keep current work moving and historical records usable.

Published Updated

Enterprise Archive or Active DMS? Where Do Records Belong? A painted blue, ivory, and gold scene pairs a laptop and working documents with indexed archive folders and a magnifying glass, labelled Active work and Governed archive.

Keep documents in active management while people are creating, revising, reviewing, or using them to complete current work. Use an enterprise archive for stable, authoritative records whose continuing purpose is controlled retrieval, evidence, retention, hold, and authorised disposition. Decide from the permitted next action and the record’s context, not its age alone.

An insurer replacing a claims application may move open claims into its new operational system while preserving settled claims in a searchable archive. A later dispute can require access to an archived claim without turning its historical evidence back into editable working documents.

Separate the lifecycle decision from the technology

A document management system (DMS) can support both active and historical records. The archive may be a governed area of the same platform or a separate application. A physical move is useful when it serves the operating model, access requirements, or system-retirement plan.

Set the boundary at the appropriate level. An approved report can be a stable record while a related case continues. An old agreement can still support active amendments. A legal hold affects permitted disposition; it does not automatically require editing the content or placing it in an active collaboration workspace.

Operating rules for current work and retained historical records.
DecisionActive document managementEnterprise archive
What work happens next?Draft, edit, approve, assemble, respond, and complete the current business process.Find, retrieve, explain, export, preserve, review obligations, and carry out authorised disposition.
How may the record change?Controlled revisions and approvals identify the working and released versions.Protect accepted historical content. Record authorised corrections, addenda, or metadata changes with their history.
Which context must remain?Current task, owner, participants, status, and relationships needed to perform the work.Original references, relevant versions, decisions, dates, relationships, access rules, and retention or hold basis.
What happens if work resumes?Open the appropriate task, case, amendment, or review under the current process.Link the new work to the preserved historical record. Follow the authorised correction or reopening rule.

Apply access, retention, hold, and audit controls in both states. The lifecycle transition changes permitted work while preserving those controls.

Define what must survive the handover

Agree the archive’s acceptance requirements while the source still exists. Identify which documents and versions are authoritative, which supporting history matters, and how users will find the record after the original application is gone.

  • Identity and relationships: source system, original identifiers, business object, attachments, related records, and links between them.
  • Content and interpretation: required originals, relevant versions, format information, integrity evidence, and any access renditions needed for use.
  • Business history: material decisions, creators, applicable dates, closure events, and the meaning of source statuses.
  • Controls: record class, retention trigger, hold status, permitted audience, and the owner of continuing review.
  • Transfer evidence: reviewed mapping, batch manifest, reconciliation results, exceptions, and acceptance authority.

An import timestamp records the transfer. Preserve the original business dates and retention-trigger information separately so a migration does not silently restart the intended lifecycle. Review source permissions and map them to the destination model; an imported customer or case identifier is not an access grant.

Keep an unreadable file, missing relationship, uncertain duplicate, or unknown owner visible as an exception. Preserve custody and assign correction or an explicit acceptance decision. A successful upload is only one part of the archive acceptance evidence. The migration verification guide covers manifests, reconciliation, retrieval tests, and cutover in more detail.

Retain the data dictionary and code lists needed to interpret exported fields and statuses after the original application retires. For Canadian federal digital archival records within its scope, Library and Archives Canada's operational standard also addresses required metadata, transfer compatibility and notification to LAC before major recordkeeping-system changes. Include the applicable consultation and transfer conditions in acceptance and retirement planning; ordinary archive import checks do not establish that those obligations are satisfied.

Choose retrieval behaviour before choosing storage tiers

Archival business status does not require slow retrieval. Decide which users need immediate access, which requests can wait, how large exports are handled, and who is responsible for a restoration request. Test the complete retrieval path, including the search result, permission check, content access, and export.

For example, AWS documents that S3 Glacier Flexible Retrieval and S3 Glacier Deep Archive objects require restoration before access. Those storage classes have different retrieval behaviour from an immediately accessible object. Match any tiering policy to the agreed service needs; calling a collection an archive does not establish that every file should use a restoration-based tier.

Usable historical access

Search by the original business reference, open permitted evidence, understand its status, and obtain an authorised export. Include the metadata and relationships needed to interpret it.

Operational recovery

Recover the archive service and its governed state after an incident. Define and test backup and restoration arrangements alongside everyday retrieval.

A backup and a business archive answer different questions. The retention, hold, and backup guide explains how recovery copies relate to record obligations. Neither an archive status nor a storage-tier change independently authorises deletion.

Worked example: retire a historical claims repository

This illustrative programme replaces an older claims application. New work will run in the replacement claims system; accepted historical evidence will remain available through an archive.

  1. 1. Classify the population

    Owners identify active claims for operational migration and historical records for archive acceptance. A settled claim with a hold remains protected under that hold; it does not need to become an editable working file simply because a reviewer may request it.

  2. 2. Preserve the claim’s explanation

    The archive mapping retains the original claim number, required evidence and correspondence, final decision, relevant versions, dates, relationships, and approved access and retention rules. Required original formats remain identifiable alongside any rendering used for access.

  3. 3. Reconcile and accept

    A delivery batch contains a document with a missing claim relationship. The team corrects it and records the reconciliation evidence. Business users test lookup by original claim number and both allowed and denied retrieval before the responsible owner accepts the batch.

  4. 4. Handle a later dispute

    The operational system opens a new review linked to the archived claim. Authorised staff retrieve the historical decision and evidence without overwriting them. New correspondence belongs to the new work and retains its relationship to the earlier record.

  5. 5. Authorise source retirement separately

    The programme confirms the remaining data, reporting, integration, recovery, and record obligations for the old application. Archive acceptance contributes to the retirement evidence; accountable owners approve shutdown and source-data handling under the agreed plan.

Review the boundary before committing to an archive

  • Identify the next permitted actions and the appropriate boundary: document, released version, business file, or whole collection.
  • Define authoritative content, required history, original references, relationships, and acceptable access renditions.
  • Preserve retention triggers, review dates, holds, and configured access without treating source identifiers as permissions.
  • Reconcile transfers and assign unreadable, missing, unmatched, or ambiguous records to accountable owners.
  • Test everyday search and retrieval, exports, restoration-based access where used, and operational recovery.
  • Agree reopening and correction rules, ongoing governance ownership, and the separate source-retirement decision.

Archive the record without losing its use

The useful boundary is between work that still needs to change and evidence that needs to remain dependable. Preserve the context, access, and continuing controls that let people use historical records. Choose the technology and storage policy around those requirements.

      Start with FormKiQ Core

      The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.

      Get Started Free

      Deploy FormKiQ Essentials or Advanced

      Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.

      Explore Options

      Plan an Enterprise Rollout

      For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.

      Book a Call