Transition to production

You cannot migrate or resume in-flight work in the new system because the earlier and later systems are not interoperable. Attempting to move active Cases without changes causes fidelity loss, broken workflows, and process incompatibility. Use the following strategies to handle existing work:

• Run-off in the older system (preferred option): Complete existing work in the old system. Create new work in SIAA going forward. Keep the earlier system accessible until all Cases are closed.
  • Ring-fence work by team, cohort, or geography.
  • This option has low risk and minimal effort but requires dual system access for a time.
• Create a new Case in SIAA: Map and transform key Case data from the old model to the new structure. This approach creates new Cases with populated context but no workflow continuity or audit trail. Manual intervention is often required to resume or reprocess work.
  • This option is more complex and introduces risk but provides visibility into earlier work.
• Hybrid approach: Combine the above strategies. Run down low-priority work, archive long-closed Cases, and selectively migrate high-value or critical open items with manual triage.
  • If there are only a few Cases, recreate them manually.

Smart Investigate Agentic Automation maintains a links table that associates Case links with transactions, which ensures that new requests, responses, or manual lookups can identify existing Cases. Porting link associations to the new solution enables continuity by surfacing old links even if the underlying case data remains outside the new system. Use the following strategies:

• Maintain the preexisting system: Use the link table to identify and access Case history in the earlier system.
• Flatten and archive: Export key data and documents from each Case into a searchable PDF or archive format. Store these in a central repository or bring them into SIAA as read-only reference records. This option does not provide process continuity but makes historical content accessible.
• Structured data migration: Map and transform key Case data from the earlier model to the new structure. This approach creates new Cases with populated context but no workflow continuity or audit trail. Manual intervention is often required to resume or reprocess work. This option is more complex but provides visibility into earlier work and might lack fidelity.