An approval tool changes while cases remain open. Decide how those cases move before replacing the interface.
Map the states
Document who can act in each state and what records support a decision. Include delegation and withdrawn requests. Existing approvals may need to remain unchanged.
Choose a transition rule
Some cases can finish in the old system; others can migrate. Describe how users identify the applicable path. Preserve references between the two systems where needed.
Test complete cases
Check a pending case, a rejected request and a changed approver. Ask for permission tests and a migration exception report. A modern screen should not obscure who made an earlier decision. Your partner's scope must include these historical transitions alongside the new workflow.
Related reading : Luxembourg client portals: modernize document history without losing context. Discuss your project scope with Sky Vaults.