What a migration moves and how it stays safe

Data DobroDesk moves

• Customers and available company or organization context
• Complete public conversation history and supported internal notes
• Attachments, tags, priority, status and available custom fields
• Source queue and assignee identifiers for mapping and audit context
• Knowledge articles and available macros as review drafts

Safety boundaries

• Imported messages never send customer notifications.
• Imported history never triggers workflows or automatic AI replies.
• Source credentials are encrypted at rest and used only while a migration is running.
• Imported conversations do not count toward usage until a customer continues the conversation.

Knowledge and saved replies

DobroDesk imports supported articles and macros as drafts. Article drafts are unavailable to AI and the widget. Macro drafts are unavailable in the composer and carry no source actions. Review article drafts under Admin > AI & Automation > Knowledge sources and macro drafts under Admin > Inbox > Macros, then activate only current business-critical content.

Reconnect external apps after cutover

1. 1

   Inventory the source help desk's installed apps and assign a business owner to each one.

2. 2

   Do not copy an OAuth token or app secret from the old help desk.

3. 3

   After the final delta, open Admin > Integrations > Data connectors.

4. 4

   Reconnect each available provider directly and review its requested scopes.

5. 5

   Test one known customer and one missing customer before retiring the source app.