Importing your agency's data

When you're setting up, you don't have to type everyone in by hand. Enmantle's import wizard brings your locations, users, clients, and certifications in from Excel or CSV files. This guide covers the order to do it in and the option for larger, programmatic loads.

Find it under Settings at Import Data — "Import locations, users, clients, and certifications from Excel or CSV files."

Import in the right order

Order matters, because later records point back at earlier ones. Users belong to locations; clients belong to locations; certifications belong to people. Import them the way the wizard recommends:

1. Locations — bring in your homes and sites first, so everything else has somewhere to attach.
2. Users — your staff, which can then be tied to those locations.
3. Clients — the people you support, assigned to their locations.
4. Certifications — credentials, attached to the users you just imported.

If you import out of order — clients before locations, say — the links won't have anything to connect to. Follow the 1‑2‑3‑4 above and it lines up cleanly.

Use the wizard

1. Open Import Data from Settings.
2. Start with Locations and follow the wizard for that step.
3. Move through Users, then Clients, then Certifications in turn.
4. Review each step before moving on.

Set your locations up thoughtfully first — the Creating locations and OSOC guide covers the fields, including the county that incident reporting needs.

For larger, programmatic loads

If you're moving a lot of data from another system, there's a second path: API Tokens, under Settings at the API tokens page. These are scoped, write-only keys for feeding data in — not for reading anything out.

• Scopes are narrow and match the import steps: import:locations, import:users, import:clients, and import:certifications.
• A token is capped at Manager role, so it can't do more than import.
• An expiration is required — every token has an end date.
• The token is shown once, at creation. Copy it then; you can't see it again.

Most agencies never need the API tokens — the wizard handles a normal setup. Reach for tokens only when you're loading data programmatically from another system.

Next steps

• Get your locations set up first.
• After users are in, assign roles and clean up any details.
• Migrating from another platform? See the export, migration, and support FAQ.