Data import
Move your existing data into Usable effortlessly: upload a file (CSV; just save Excel as CSV), columns and the delimiter are auto-detected, duplicates flagged — then import.
M03 · Core · System core
your-address.usable.works| Target module | File | Source | Status | Imported | Errors | Started |
|---|---|---|---|---|---|---|
| Service due | Bauer & Co. | Done | In progress | Record 3 | Entry 2 | 07/06/2026 |
| Defect reported | Wolf Spedition | Reviewed | Done | Item 4 | Record 3 | 18/06/2026 |
| Handover ok | Roth Handel | Open | Reviewed | Entry 5 | Item 4 | 29/06/2026 |
| Re-check | Meyer GmbH | In progress | Open | Record 6 | Entry 5 | 10/07/2026 |
| Routine checked | Kraus Logistik | Done | In progress | Item 7 | Record 6 | 21/07/2026 |
What you do here
First pick the target module (e.g. Contacts or Vehicles), then upload the file. Without AI, Usable detects the delimiter (including the German semicolon), maps source columns to fields via heuristics, translates option lists (e.g. "open" → status) and resolves references like customer or vehicle by name to an existing id. In step 3 you pick a match field for duplicate detection and see, before importing, how many rows are new, duplicate or incomplete. For Excel, save it as CSV in Excel; a real database connection is handled by the professional migration.
Tips
The first CSV row must contain the column headers. Set columns you don't need to "ignore". If you want it perfect, you can add the professional migration later.
Traceability & law
Every import is logged as a run: target, source, time, counts (new/duplicate/incomplete/error) and who ran it. Because an import almost always moves personal data (contacts, employees, customers, clients), you document the data's origin and the legal basis under Art. 6 GDPR for each run – part of your record of processing activities (Art. 30). Every imported row is tagged internally as "imported" plus the run id. Import health data (Art. 9) only into modules built for it.
Undo & fixing errors
If something went wrong, open the run and roll it back – the imported rows are removed again via the run id. The error report lists every flagged row with its column, field and reason; fix the source file and import again. That keeps the import repeatable without piling up duplicates.
What's inside
- Data import
- Import runs
- Import run
- Roll back import
- Delete log
Fits together with
Other blocks from the same area.
- DashboardThe dashboard is your home screen: an operational overview of every area you have access to – a traffic light per area, numbers that need action, a 30-day due-date timeline and status distributions.
M01 - SettingsThis is where your company's central settings live, used by all other modules.
M02 - UsersThis is where you manage who has access to the app, what state each account is in (invited, active, deactivated) and which role and permissions each person gets.
M04 - RecordsThe tamper-evident logbook of the app: who did what, and when. System events are recorded immutably (append-only); manual cases – on safety, maintenance or incidents – are tracked with a status. You read it as a chronological timeline.
M05