Importing the CSV exports

Fill a snapshot from the admin-console exports: no API key for the data, seconds on tens of thousands of accounts, and three facts a scan cannot reach.

What it is. The other way to fill a snapshot. Atlassian Administration can export your whole directory as CSV; the app reads those files in your browser, keeps only the normalised rows, and builds the same snapshot a scan builds — every tab works on it identically.

Why you would. Three reasons. It is fast: tens of thousands of accounts in seconds, where a scan of the same organisation is a long background job. It needs no API key for the data — the files come from your own admin console. And it carries three facts no API will hand a scan: who your organisation admins are, Atlassian's own Guard billing flag per account, and whether single sign-on is enforced — which is also what makes the 2FA and Guard filters, and much of the Admin roles page, light up.

The two files

File	Where it comes from	What it carries
Managed accounts export	admin.atlassian.com → Users → “…” menu → Export managed accounts	One row per managed account: status, last-active dates per product and per site, the Guard billing flag, verified email, two-step verification, single sign-on.
Users and groups export	admin.atlassian.com → Users → “…” menu → Export users	One row per group membership — who is in which group — plus the Org role column that names your organisation admins outright.

Export with all columns

The app validates the headers before importing and names any column that is missing. If the admin console asks which columns to include, include them all — a narrowed export is recognised and refused with the list of what it lacks, rather than silently importing less.

How the import runs

1On the Dashboard, click Scan Users — the dialog that asks about scope also offers the import, under “Already have your Atlassian Administration exports?”.
2Drop in one file or both. The app recognises which is which; order does not matter.
3Answer “Which of these sites are yours?” — the one judgement call the files cannot make for you, explained below.
4Choose the scope: everyone in the file, or only people holding a product on the sites you ticked.
5Watch the progress in the dialog. The import runs through the same background pipeline as a scan, so leaving the page does not lose it, and the Dashboard shows it running like any scan.

Which sites are yours — why it asks, and what it pre-ticks

The export lists every site each person can reach, including other companies' instances — a consultant on your domain appears with their customers' sites. Ticking a site as yours decides one number: how many of your people hold access outside your organisation, which feeds the Guard block's “working elsewhere” figure and the Access reaches filter. The app pre-ticks your busiest site, anything sharing its name or holding many of the same people, every sandbox, and Bitbucket and Trello — those are Atlassian's own addresses, not another company's instance. Review the list; it is a heuristic, stated as one.

Sandboxes are set aside, not counted: a sandbox seat comes with a Premium or Enterprise plan rather than being billed per user, and on one measured customer it was 43.9% of all product grants — counting it would nearly double the reported waste.
A plan tier is not a site. The Trello column carries values like Free; the import knows the difference and does not invent a site called Free.
Whole-file imports see the most. A scoped import has the same blind spot a licence scan has — accounts holding no seat are left out — and the dashboard says so where it matters.

What still needs the API key

Everything that changes an account: removing groups, revoking products, suspending, restoring — and the API-token sweep. The import replaces the reading, not the acting. It is the right first step for a security review, a one-off analysis, or evaluating the app before your organisation approves a key.

Importing another organisation's exports

The files never leave your browser as files — only the normalised rows are stored, inside your own site. Be aware that importing a directory makes this installation hold those people's account IDs, names and emails, with everything that implies: they enter the snapshot, the filters, and the app's daily personal-data report to Atlassian, until a newer snapshot replaces them or you uninstall.