# Field-map preview with explicit skips before ticket import

> Show switchers exactly which fields will map, which will be skipped, and which need a new destination field before they start the migration.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/field-map-preview-with-explicit-skips-before-ticket-import/
- 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: uncommon
- Budget: low
- Channels: Product, Support, Sales
- Stages: migration, data mapping, evaluation, support
- Key metric: Intercom positions the native importer for migrations under 150k tickets.

## Why this can grow

Migration fear usually hides in the sentence 'we'll figure out the data later.' A mapping screen does the opposite. It turns vague risk into concrete choices the buyer can inspect. Intercom makes this useful by auto-mapping what fits, marking the rest to skip, and letting the team create new fields when needed. That shortens implementation calls, surfaces limitations early, and makes the switch feel legible instead of magical.

## 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 field-map preview with explicit skips before ticket import can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Support 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's Zendesk importer auto-maps appropriate fields, marks others to skip, and lets the user create a new field in Intercom when the incoming field needs a destination.

## Adjacent tactics in the same lane

- [Default owner routing for import edge cases](/growth-ideas/default-owner-routing-for-import-edge-cases/) - same source, 2 shared channels, 1 shared stage
- [Simplest-form history import for reporting continuity](/growth-ideas/simplest-form-history-import-for-reporting-continuity/) - 2 shared channels, 2 shared stages
- [Batch test migration on sample records first](/growth-ideas/batch-test-migration-on-sample-records-first/) - 2 shared channels, 2 shared stages
- [Workflow exceptions before API-led migration](/growth-ideas/workflow-exceptions-before-api-led-migration/) - 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.