Intercom's Zendesk Article Importer Ends April 25, 2026: What SaaS Teams Should Do Now

What's Actually Changing on April 25, 2026

Intercom has confirmed that its legacy Zendesk article importer will be permanently deprecated on April 25, 2026. If you've been using this integration to sync your Zendesk knowledge base articles into Intercom — either automatically (daily sync) or manually — that pipeline stops working after this date.

Here's what Intercom's own documentation says will happen:

• Automatic daily syncs will stop. If you have a scheduled sync running, it won't trigger after April 25.
• Manual syncs will stop. You won't be able to trigger a manual import through the legacy tool.
• One-time imports remain possible — but only if you act before the deadline.

Intercom is pushing users toward its newer article import tooling, but the transition isn't seamless — and for many SaaS teams, this deprecation is a forcing function to re-evaluate a stack that was already showing cracks.

Who Is Affected

You're affected if your team:

• Previously migrated from Zendesk to Intercom and kept Zendesk as a secondary knowledge base
• Uses Zendesk for ticketing while serving Intercom articles to end users
• Relies on the legacy Zendesk-Intercom sync to keep help content in sync across both platforms

If you're running both Zendesk and Intercom simultaneously — a surprisingly common pattern among mid-sized SaaS companies — this change directly impacts your knowledge management workflow. Teams in this situation are often paying $300–$800+/month across both tools to get functionality that a single modern platform could deliver for far less.

Your Three Options Right Now

Option 1: Migrate to Intercom's Newer Import Flow

Intercom offers a newer article import workflow that replaces the legacy Zendesk importer. Before April 25, you can run a final one-time sync using the legacy tool, then transition to the new approach. This is the path of least resistance if you're committed to staying on Intercom.

The catch: Intercom's newer flow doesn't support ongoing automated sync the way the legacy tool did. You'll likely need to manage article updates manually or through custom API integrations going forward. And if you're already frustrated with Intercom's pricing — particularly the Fin AI per-resolution fees that can balloon to $0.99 per resolved ticket — this is another operational burden piled onto an already expensive platform.

Option 2: Export Articles and Re-import Manually

Export your Zendesk knowledge base articles (as HTML or via API), then import them directly into whatever platform you're using. This is a one-time migration that gives you full control but requires manual effort. Depending on how many articles you have, this could take anywhere from an afternoon to several days of content cleanup.

Key considerations for manual migration:

• Inline images need to be re-hosted (they'll still reference Zendesk CDN URLs after export)
• Internal links between articles will break and need to be updated
• Article formatting often degrades when moving between platforms
• Metadata (tags, categories, publish dates) requires manual remapping

Option 3: Rethink Your Support Stack Entirely

This is the option most SaaS teams should at least evaluate. If you're currently running Zendesk and Intercom as separate tools and duct-taping them together with sync integrations, the April 25 deprecation is a signal: the integration tax is getting higher, not lower.

The better question isn't "how do we preserve the sync?" — it's "why are we paying for two platforms when one modern tool should handle everything?"

The Real Problem: Running Two Platforms Is Expensive and Fragile

The Zendesk + Intercom dual-stack is common, but it's a symptom of tools that were built for different eras. Zendesk was designed as a ticket management system. Intercom was designed as a messaging and engagement platform. Neither was built from the ground up to handle the full modern support workflow: AI-powered chat, knowledge base, bug reporting, user surveys, product roadmap, and proactive in-app messaging — all from one place.

When companies try to solve this by layering Zendesk on top of Intercom (or vice versa), they end up with:

• Duplicate knowledge bases that drift out of sync
• Complex API integrations that break with every product update
• Support agents switching between multiple dashboards
• Billing for overlapping features on two platforms
• Integration dependencies like the Zendesk importer that get deprecated without warning

The April 25 deadline is a natural moment to ask: what if you didn't need the integration at all?

What Gleap Does Differently

Gleap is built as a single platform for the entire customer support and product feedback loop — no integrations required between your own tools. Instead of syncing a Zendesk knowledge base into Intercom, Gleap includes a native knowledge base that's directly connected to the same AI that powers your support chat.

Here's what that looks like in practice:

• Knowledge base built in: Write articles once in Gleap's editor. They're instantly available to your AI agent (Kai), your live chat, and your customers — no sync required.
• AI that uses your knowledge: Gleap's Kai AI agent draws on your knowledge base to answer questions automatically. When a customer asks something, Kai searches your articles, generates a response, and escalates to a human only when needed.
• Transparent pricing: Gleap's Team plan is $149/month (or $119/month billed annually) — unlimited team members, all features included. Compare that to Intercom's $0.99 per AI resolution layered on top of a base seat-based subscription, or Zendesk's per-agent fees.
• One dashboard: Your team handles everything in one place — shared inbox, AI chat, knowledge base, bug reports, feature requests, surveys, and in-app messaging.

For the 4,500+ SaaS companies already using Gleap, the knowledge base isn't a bolt-on integration — it's a first-class part of the support experience. Articles train the AI, reduce ticket volume, and are searchable by customers directly from the in-app widget.

How to Migrate Your Knowledge Base to Gleap

If you're considering this as your moment to consolidate, here's a practical migration path:

1. Export your Zendesk articles before April 25 using Zendesk's built-in export or the API. Export as HTML for cleanest formatting.
2. Audit your content. Identify which articles are still accurate and worth migrating. Most knowledge bases have 30–40% outdated content that doesn't need to follow you to the new platform.
3. Import into Gleap's knowledge base. Gleap supports manual creation and bulk import. Re-host any inline images via Gleap's media library to ensure they always load.
4. Connect your AI. Once your articles are in Gleap, Kai automatically indexes them. Test a few queries to verify it's pulling the right content in responses.
5. Install the Gleap widget. Gleap supports iOS, Android, Flutter, React Native, JavaScript, and more. The widget exposes your knowledge base, live chat, bug reporting, and AI — all in one in-app experience for your users.
6. Cancel your redundant tools. Once Gleap is live, you likely won't need separate subscriptions to both Zendesk and Intercom. The savings typically more than cover Gleap's $149/month Team plan.

Start a free trial at gleap.io/pricing — no credit card required.

What About Teams That Want to Stay on Intercom?

If you're committed to Intercom, here's your checklist before April 25:

1. Run a final manual sync via the legacy Zendesk importer to capture any recent updates
2. Download a backup of all your Zendesk articles (HTML or JSON via API)
3. Review Intercom's updated import documentation and set up the new workflow
4. Update any internal links in articles that reference Zendesk-specific URLs
5. Re-test your knowledge base search results in Intercom to verify content accuracy

That said, it's worth doing the math on what you're actually paying. If you're using both Zendesk (at $55+/agent/month) and Intercom (base price plus Fin AI resolution fees), a consolidated platform like Gleap or another Intercom alternative could deliver the same capability at a fraction of the cost.

Frequently Asked Questions

What exactly is Intercom deprecating on April 25, 2026?

Intercom is disabling its legacy Zendesk article importer — the tool that allowed teams to sync their Zendesk knowledge base articles into Intercom's Help Center, either automatically (daily) or manually. After April 25, these syncs will stop. One-time imports before that date are still possible.

Will my existing synced articles in Intercom be deleted?

No. Articles that were already synced and exist in Intercom's Help Center will remain. The deprecation only stops future syncs — it does not delete content that's already been imported.

Can I still migrate from Zendesk to Intercom after April 25?

Yes, but the legacy importer won't be available. You'll need to use Intercom's newer article import workflow or migrate content manually. Check Intercom's updated documentation for the current recommended approach.

How much does it cost to run both Zendesk and Intercom simultaneously?

Costs vary widely based on team size and usage, but it's common for mid-sized SaaS teams to spend $500–$2,000+/month across both platforms. Zendesk starts around $55/agent/month; Intercom's pricing includes a base subscription plus Fin AI resolution fees of $0.99 per resolved ticket.

What is Gleap and how does it replace both tools?

Gleap is an all-in-one customer support platform that includes live chat, AI support (via Kai), a native knowledge base, in-app bug reporting, feature voting, and product surveys. It replaces the need for both a ticketing platform (like Zendesk) and a messaging/knowledge platform (like Intercom) at a flat rate of $149/month for the Team plan — unlimited users and projects.

Does Gleap's AI use my knowledge base articles?

Yes. Gleap's AI agent Kai automatically indexes your knowledge base articles and draws on them when answering customer questions. This means articles you write directly reduce ticket volume — no manual training steps required.

How long does it take to migrate a knowledge base to Gleap?

For most SaaS teams with 50–200 articles, a migration takes 1–3 days including content review, re-importing, and testing the AI responses. Gleap's onboarding team can help with larger migrations.

Is Gleap a good fit for mobile apps?

Yes — Gleap has native SDKs for iOS, Android, Flutter, and React Native. It's designed for both web and mobile, with the in-app widget surfacing your knowledge base, chat, and bug reporting directly inside your product.

---

Make the April 25 Deadline Work for You

Most SaaS teams will treat the Intercom Zendesk importer deprecation as a technical problem to solve before the deadline. The smarter move is to treat it as a strategic opportunity.

If your support stack is a patchwork of overlapping tools with syncs, integrations, and dependencies that break every few months — this is your moment to consolidate. Gleap gives you everything in one platform: AI-powered chat, a native knowledge base, bug reporting, feature requests, surveys, and live chat — for less than you're probably paying for either Zendesk or Intercom alone.

Start a free trial at gleap.io — no credit card required. Or explore how Gleap compares as a Zendesk alternative and an Intercom alternative.