Adapt this guidance to your policies, Cloud plan, identity model, channels, provider accounts and legal requirements. Validate every production change in a controlled workspace.
Prerequisites
Collect these decisions and controls before beginning the workflow.
- A named owner for the workflow and the authority to approve customer-impacting changes.
- A non-production workspace or controlled test scope with safe sample data.
- Current channel, identity, retention, access and escalation requirements.
- A rollback or disable path if acceptance criteria are not met.
Inventory the current system
List channels, queues, users, roles, automations, integrations, fields and retention obligations.
Clean before importing
Remove obsolete accounts, duplicate knowledge and unnecessary historic data.
Build the target model
Create sites, departments, roles, priorities, SLAs and customer fields before moving production traffic.
Run a pilot
Migrate a limited team or channel and verify identity, threading, attachments and reporting.
Cut over with rollback
Freeze configuration changes, communicate ownership and retain a documented fallback window.
Implementation checklist
- Record the current state, target outcome and measurable acceptance criteria.
- Configure the minimum viable workflow before adding automation or provider complexity.
- Test customer, agent, manager and failure experiences end to end.
- Document ownership, monitoring, review cadence and escalation contacts.
- Recheck the workflow after product, provider, policy or team changes.
Troubleshooting and recovery
The configured result differs from the documented workflow
Return to the smallest reproducible scope, compare current configuration with prerequisites and inspect the latest change.
The workflow works only for administrators
Review roles, site scope, provider permissions and object ownership using a non-administrator test account.
Customers receive duplicate or delayed outcomes
Inspect idempotency, provider delivery attempts, queue retries, threading and automation overlap.
A provider or channel becomes unavailable
Use the documented fallback, pause unsafe automation and communicate ownership until service is restored.
Imported counts do not reconcile
Stop cutover, preserve source data, inspect mappings and rerun a dry import before accepting the migration.