AssetSort
All help sections· Bulk Actions & Data

BLK · Bulk Actions & Data

Exporting and importing an organisation

Move configuration — or a whole organisation — between workspaces.

3 min read

An organisation can be exported as a single .json file and imported elsewhere in AssetSort: into another organisation you run, or as a brand-new managed client. It's how you copy your setup to a new workspace, bring a customer's estate under your MSP, or keep an offline copy. Export and import live in Settings → Organization → Import & export, and both are for the owner (for a client, your MSP's owners and admins too). An archived organisation can still be exported, but nothing can be imported into it until it's restored. To bring a file in as a new managed client, use Import client on MSP → Clients. There's still no CSV or spreadsheet import.

  1. 01

    Export

    Choose Export. By default the file holds the organisation's configuration — custom fields, custom types and settings. Tick Include all organization data to add every hardware, licence and certificate record, plus people, tags, folders, assignments and links. Not included either way: members and invitations, uploaded documents, activity history, alerts and Microsoft 365 sync state — a new organisation restores those through its own connection. On MSP → Clients, Export data in a client's row menu downloads a full export (all data included) of that client.

  2. 02

    Import into an organisation you already have

    Choose Import, drop the file in, and pick which custom fields and types to bring across; entries this organisation already has are marked Already exists and skipped. Nothing already here is changed or removed, and the file's settings (currency, alert window, lifecycle, branding, contact) are never applied — this organisation keeps its own. If the file holds records, tick Also import all organization data to add them as new records with their assignments and links; tags, people and folders that already exist here (same name, same email, same folder path) are reused rather than duplicated, and hardware whose serial number is already here, or certificates already tracked here, are skipped — the completion message and the activity log say what was skipped and why. Every row is checked as a form would check it: an unknown status or type, a negative cost or one with more than 2 decimal places, a purchase date in the future, or a spare while spares tracking is off here refuses the whole file, naming the rows, and nothing is imported. Imported records are managed by hand from then on — Microsoft 365 links, documents, alerts and history don't travel with the file. Your plan's item limits apply to the whole import — it goes in completely or not at all.

  3. 03

    Import as a new client

    On MSP → Clients, Import client creates a new managed client from an export made with Include all organization data: give it a client name and choose Create client. Everything in the file is recreated in the new client (a configuration-only file also works — the client then starts empty with its custom fields and types), and it counts towards your plan's managed-client allowance.