# Default owner routing for import edge cases

> Give the importer a default team, teammate, or fallback contact so odd records land somewhere safe instead of blocking the whole switch.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/default-owner-routing-for-import-edge-cases/
- Source: [intercom.com](https://www.intercom.com/help/en/articles/9307237-import-your-zendesk-ticket-user-and-organization-data)
- GrowthDex source hub: [Intercom Help: Import your Zendesk ticket, user and organization data](/sources/intercom-help-import-your-zendesk-ticket-user-and-organization-data-inte/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: low
- Channels: Support, Operations, Product
- Stages: migration, risk control, switcher intent, implementation


## Why this can grow

Real migrations always contain bad rows, deleted users, or records that do not map cleanly. If every exception becomes a blocker, the migration stalls and confidence drops. A fallback owner route keeps momentum. The import still finishes, the data still lands in a reviewable state, and the buyer can clean up the exceptions after seeing the system work end to end.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where default owner routing for import edge cases can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Operations channel.
3. Use the evidence from intercom.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Intercom requires teams to choose a default team and teammate when Zendesk mappings are not possible, and routes deleted or inactive-user records to a default inactive contact so the import can still complete.

## Adjacent tactics in the same lane

- [Field-map preview with explicit skips before ticket import](/growth-ideas/field-map-preview-with-explicit-skips-before-ticket-import/) - same source, 2 shared channels, 1 shared stage
- [Full transcript reply instead of message-by-message replay](/growth-ideas/full-transcript-reply-instead-of-message-by-message-replay/) - 2 shared channels, 2 shared stages
- [Dry-run validation before support-data import](/growth-ideas/dry-run-validation-before-support-data-import/) - 3 shared channels, 1 shared stage
- [History structure choice before support import](/growth-ideas/history-structure-choice-before-support-import/) - 2 shared channels, 2 shared stages

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The switch page should finish the move](/blog/the-switch-page-should-finish-the-move/) - SaaS SEO, product-led growth, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.