Hi,
As part of reorganisation, we would like to move inflight case data from one stack to another in production.
Can someone share the steps and precautions that we need to know while moving the open cases data.
Hi,
As part of reorganisation, we would like to move inflight case data from one stack to another in production.
Can someone share the steps and precautions that we need to know while moving the open cases data.
First make both stacks run the same app version and have the same data schema. Schedule a short read only window, stop new case creation, and pause queue processors, agents, listeners, and inbound integrations so work drains cleanly. Back up both sides and export a list of open case IDs for reconciliation. Move data with a controlled database migration of work and related tables or use BIX export then import; include Assign, History, Index, Link Attachment, Data WorkAttach, and only needed queue data. If attachments live in a repository like S3, copy those files too and keep the same paths so metadata still works. Preserve pzinskey and case IDs and make sure operators, access groups, and work queues exist or are remapped to avoid broken assignments. After load, rebuild search indexes and SRS indexes and run revalidate and save if any rules changed. Spot check cases end to end to confirm you can open attachments, see correct assignments, and that SLAs and timers resume normally. When checks pass, unpause agents and queues and reopen intake, and keep a rollback plan if counts or health checks fail.