Keep records and replace outdated standalone links
Use current navigation after the merger and verify that historical evidence remains accessible through the intended record.
Before you start
Use current navigation after the merger and verify that historical evidence remains accessible through the intended record.
Follow these steps
- Open an existing property, compliance record and protected evidence file from the current menu.
- Compare their references and relationships with the intended business records.
- Replace staff bookmarks with the current merged workspace route.
- For an old recipient link that fails, use the merged record’s supported reissue workflow after checking recipient, purpose and validity.
- Ask an authorised administrator to investigate missing historical evidence through the current workspace storage and source record. SaaS tenants cannot fall back to shared legacy file paths.
Check it worked
Current staff and recipient journeys use the merged routes and retain access to the correct historical evidence.
If something does not look right
Some old top-level standalone compliance or renewal URLs cannot be intercepted by the single merged module. Reissuing through the supported workflow is preferable to guessing a replacement URL or copying a token into another path.
Questions and answers
Should the old standalone Compliance Monitor stay active?
The combined installer deactivates its old lifecycle after successful setup. Historical files may still be needed; deactivation is different from deletion.
Does uninstall delete business records?
The merged module’s uninstall/deactivation behaviour preserves business data and files.
How should historical evidence be moved?
Use an authorised migration that preserves the source record, workspace relationship and protected file access. Verify the evidence through its supported record link afterwards.