Zendesk Organization Import template.

What's inside — the exact file

This is the complete template, not a sample. The rows are worked examples — replace them with your data (and delete them before any platform import).

What this template is for

Organizations are how Zendesk groups end users by company, and this template bulk-creates them — with the domain mapping, sharing flags, and tags that make organizations actually useful rather than just labels. The columns follow Zendesk's documented organization-import format as of July 2026.

Run this import before your user import: users reference organizations by name, so organizations must exist first. It matters most for B2B support, where routing, SLAs, and reporting all hang off which company a requester belongs to.

How to use it, step by step

1. Build your organization list from the system of record. Export accounts from your CRM rather than your old help desk if you can — CRM company data is usually cleaner, and it aligns support with how sales already names things.
2. Fill the domain mapping. The default column holds email domains (e.g. example.com); anyone who registers with a matching email is auto-added to the organization. This one column does more routing work than most triggers.
3. Decide sharing flags honestly. shared lets every user in the organization see each other's tickets; shared_comments lets them comment. Default both to FALSE and enable per-organization only where the client explicitly wants shared visibility.
4. Carry external IDs. Put your CRM account ID in external_id so re-imports update instead of duplicate, and so a future CRM integration has a stable join key.
5. Delete example rows and import. Upload via Admin Center → People → Bulk actions. Then run your user import — users will attach to these organizations by exact name match.

What each column means

Common mistakes to avoid

• Importing users first, then organizations — the user import's organization column will match nothing.
• Turning shared on for every organization by default and accidentally exposing tickets between a company's departments or subsidiaries.
• Mapping generic domains (gmail.com, outlook.com) in the default column — every consumer signup would join that organization.
• Slightly different names between this file and your user import file — the match is exact, so 'Acme Inc' and 'Acme Inc.' are two different organizations.

Questions, answered

Why do organizations matter for SLAs?

SLA policies and triggers can target organization tags and fields, which is how VIP or contract-tier service levels are usually implemented — the ticket inherits its requester's organization, and the policy keys off it.

Can a user belong to multiple organizations?

Yes, Zendesk supports multi-organization membership for end users, but the CSV import assigns the primary organization only — additional memberships are set in the UI or via API afterward.

What does the default domain column actually do?

Any new user whose email matches a listed domain is automatically added to that organization at signup — routing and visibility rules then apply with zero agent effort. It's the highest-leverage column in the file.

This is a Market Disrupt worksheet, not a vendor file. Import-format templates follow each platform's documented layout as of July 2026 — platforms evolve, so validate against current documentation before a large import.