Imports & Exports

What this does for you

Imports let you bring data into the platform in bulk instead of typing it in one record at a time — upload a spreadsheet and the platform will match your file's columns to the right fields and add or update those records for you. This is the fastest way to get set up if you're moving from another system or have a large batch of records to load at once.

Exports let you take data back out — download a filtered list of records as a CSV, Excel (XLSX), or JSON file, so you can report on it, back it up, or hand it off to another tool.

Who can use it

• Importing data requires your role to have import permissions, granted by your account administrator. Viewing import history, starting a new import, and managing/downloading an import's files are each controlled separately (import.view, import.create, import.edit for the field-mapping screen, and import.manageFields / import.download for those specific row actions), so it's possible for your role to view import history without being able to start a new one, or vice versa.
• Exporting data is available from any of the platform's list pages via their Export button, and from the dedicated Exports page. Unlike Imports, exporting today has no permission check of its own — if you can see a list page and your organization has the Exports feature turned on, you can export from it.

If a button is greyed out for you, hover over it — the platform will tell you which permission is missing so you know who to ask.

Where to find it

• Imports — /settings/imports
• Exports — /settings/exports, or the Export button on any data list page

How to use it

Importing data

1. Go to Settings → Imports and click + Add import.
2. On the Select collection screen, pick what you're importing. Current options include Company, Contacts, Plan, Product, Subscription, Features, Invoice, User, Usage Source, Usage Compilation, Billing Units, Usage, Markets, Proposals, Upsell/Downsell, and Self-serve Checkout. (A "Migrate from another platform" tile is also shown here, but it isn't an import type itself — it just takes you to the separate Migrations page.)
3. On the next screen, optionally click Download under "Sample data" to get a template file with the exact column headers the platform expects for that collection.
4. Click the upload area to choose your CSV or JSON file, then choose an Action: Create new and update, Update only, or Create only. (Usage imports skip this choice — they're always created new.)
5. Click Create. Your file is uploaded and the import appears in your Imports list.
6. From the Imports list, use the row menu's Manage Fields action to open the Configure Fields screen. Match each column from your file (Source column) to the matching field in the platform (Destination property) — most obvious matches are already suggested, and any source column that can't be mapped shows as "Not applicable" / "Not mapped."
7. The screen's main button walks through Map Fields → Validate → Upload. Validate checks your data (required fields present, correct types, valid values) and shows a pass/fail message per mapped field; confirm the Upload step once you're happy.
8. Your data is processed in the background. The Configure Fields screen shows "Uploading Data" while it's in flight; the Imports list shows the same in-progress state as "Upload Pending," moving to a final Upload Successful or Upload Failed once it's done. You can leave the page and check back later.
9. From the Imports list, use the row menu's Download action at any time to get back the original file you uploaded.

Exporting data

1. From any data list, click the Export button.
2. Choose a Rows scope — All records, or the list's current filtered/unfiltered view — and optionally check Include columns hidden in this view.
3. Choose a file format: CSV, XLSX, or JSON.
4. Click Export. If an export with the same fields and filters was created recently, you'll be asked to confirm before another one is generated.
5. Small exports download immediately. Larger exports are generated in the background — you'll get a toast telling you it's generating and that you'll get an email when it's ready.
6. Visit the Exports page any time to see all your organization's past exports (status: Pending, Completed, or Failed) and re-download a completed one from the row's download icon.

Tips / things to know

• Imports always process in the background, even for a single row — the "Upload Pending" status you see isn't a bug, it's the normal in-progress state while the platform commits your data.
• The field-mapping screen greys out any source column that can't be mapped to anything for the collection you're importing, so you always know at a glance which columns will be used.
• There's no per-field picker on export anymore — you choose all fields (optionally including hidden columns) or the platform's default view, plus whatever filters are already active on the list you exported from.
• Exported file links are not permanently protected — treat a downloaded export file the same way you'd treat any other exported spreadsheet containing your business data, and avoid sharing the link itself outside your organization.
• If some rows in your import fail (for example, a required field left blank), the platform currently only shows you validation results per mapped field, not a row-by-row breakdown — double-check your source file against those messages before uploading.
• Not every field on a record is available to map when importing — a small number of internal/system fields are intentionally excluded and won't appear as mapping destinations.
• Exporting has no role-level permission gate today — anyone who can see a list page (and whose organization has Exports turned on) can export it, regardless of what other permissions their role has.