The April 25, 2026 deadline for Intercom's legacy Zendesk article importer has passed. Intercom's help documentation says the older importer stops both automatic daily syncs and manual syncs after that date. To keep Zendesk article syncing active, teams need to migrate to the newer importer workflow described in Intercom's Zendesk sync documentation.
For SaaS teams, this is more than a small admin task. If your knowledge base lives in Zendesk, your customer conversations happen in Intercom, and AI answers depend on synced articles, a stopped sync can quietly create stale support content.
What Changed After April 25
According to Intercom's documentation, the legacy importer no longer runs after the deadline. That means:
- Automatic daily syncs from the legacy importer stop.
- Manual syncs from the legacy importer stop.
- Teams can migrate to Intercom's newer importer experience.
- After migration, teams should review filters, audiences, tags, and AI settings.
The practical risk is content drift. If an article is updated in Zendesk but Intercom's old sync is no longer running, customers and AI tools may see outdated answers until the source is migrated or content is managed somewhere else.
Who Should Care
This change matters if your team uses Zendesk Guide as the source of truth while also using Intercom for Messenger, Help Center, Fin, Copilot, or support conversations. It also matters if your team migrated from Zendesk to Intercom but kept Zendesk content around during the transition.
The more your support stack depends on synced articles, the more important it is to audit the migration. Broken article syncs can affect help center search, AI answer quality, internal agent suggestions, and links inside workflows.
Your Options Now
Option 1: Migrate to Intercom's New Importer
If you want to stay with Intercom and Zendesk, follow Intercom's migration flow for the Zendesk source. After migrating, check metadata filters, tags, article visibility, AI audience rules, and links from workflows to articles.
This is the lowest-change option, but it keeps the same cross-platform dependency in place. Your team still needs to manage how Zendesk content powers Intercom experiences.
Option 2: Export, Clean Up, and Rebuild Your Help Center
If your knowledge base has grown stale, the deprecation can be a useful forcing function. Export your Zendesk articles, identify outdated content, consolidate duplicates, update screenshots, and rebuild the help center in the platform you want to maintain long term.
Pay special attention to images, internal article links, category structure, redirects, article ownership, and any content that AI tools should not use.
Option 3: Consolidate Support Content and Customer Conversations
Running Zendesk and Intercom together can make sense for some enterprise teams, but many SaaS teams end up paying an integration tax: duplicate content, sync failures, agent context switching, and overlapping subscriptions.
If you are already reviewing the workflow, it may be worth comparing a single-platform setup. Gleap combines a knowledge base, AI support, live chat, in-app bug reporting, surveys, feature requests, and roadmap workflows in one place.
How Gleap Handles This Differently
In Gleap, the knowledge base is connected directly to support and AI workflows. Kai can use approved help content to answer customer questions, and human agents can share articles from the same inbox where conversations, feedback, and bug reports live.
That reduces the need to sync one help center into another messaging tool. It also keeps product feedback closer to support content. If users repeatedly ask the same question, the team can update an article, adjust onboarding, or add a product improvement without hunting through multiple systems.
Teams evaluating a move from Zendesk can start with the Zendesk alternative page. Teams comparing Intercom costs and workflow coverage can review the Intercom alternative page or current Gleap pricing.
Migration Checklist
- Back up your content. Export Zendesk articles, images, categories, labels, and article URLs before changing sync settings.
- Audit article quality. Remove outdated content, merge duplicates, and flag articles that should not power AI answers.
- Migrate or rebuild. Use Intercom's newer importer if staying with Intercom, or move approved content into your new knowledge base.
- Check links and images. Re-host images where needed and update internal links that still point to Zendesk URLs.
- Test search and AI answers. Ask common support questions and confirm customers receive current, accurate content.
- Update team workflows. Make sure support agents know where articles now live and how updates should be requested.
Bottom Line
The legacy importer deprecation is a sync problem, but it points to a bigger operational question: where should your support knowledge live, and how many tools should depend on it?
If Intercom and Zendesk still make sense for your team, migrate the importer and audit the result carefully. If the sync has become one more fragile piece of a complicated stack, this is a good time to consolidate knowledge base, AI support, feedback, and customer conversations into one workflow.