Limitations of Zendesk Multibrand Migration
What are the limitations of migrating to Multibrand in Zendesk?
Migrating to Multibrand in Zendesk comes with several limitations. For instance, ticket events and IDs cannot be migrated, and Help Center content like article creation dates and comments are not available post-migration. User information such as end-user passwords and agent roles also cannot be migrated. Additionally, workflows like views, triggers, and automations need to be reviewed and adjusted for the new brand setup.
More related questions
What are the prerequisites for migrating from Hub and Spoke to Multibrand in Zendesk?
Before migrating from Hub and Spoke to Multibrand in Zendesk, ensure you're actually using all your spokes. If your spokes aren't being used or aren't sharing tickets with the hub, a migration might not be necessary. Additionally, remember that a…
How does the behavior change when migrating from Hub and Spoke to Multibrand?
Migrating from Hub and Spoke to Multibrand in Zendesk involves several behavior changes. For instance, all agents will have access to all brands by default, and you can create brand views for agents. Additionally, there's only one signature per…
What are the steps and timeline for migrating to Multibrand in Zendesk?
The migration to Multibrand in Zendesk involves several steps, including configuring your Multibrand instance, verifying sample content migration, and preparing for downtime. The timeline depends on Zendesk resources, migration complexity, and your…
Can I migrate Help Center communities when moving to Multibrand?
Yes, you can migrate your Help Center community content when moving to Multibrand using the Help Center API. However, note that some settings and content, like article creation dates and comments, won't be available post-migration. It's important…
How does Zendesk handle agent permissions in a Multibrand setup?
In a Multibrand setup, all agents have access to all brands by default. However, you can create brand views for agents to use. If you need to restrict access, you can use triggers to assign brand tickets to specific groups and restrict agent…
What happens to ticket forms during the migration to Multibrand?
During the migration to Multibrand, you can restrict access to specific ticket forms by brand. This allows you to control which ticket forms are available to end-users and agents based on the brand of the Help Center or ticket they're viewing. This…
Interested indeflectingover 70% of your Zendesk support tickets?
Zendesk Support Tickets
Zendesk Messaging (live chat)
Join1,000+ companies reducing their support costs and freeing up support agents for more important work
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
Reduce support costs.Spend more time on customer success.
