Preview before writing
Review parsed rows and validation results before a supported import changes Serberus data.
Move data with a review step
Preview supported imports before they change records, then export the operational data you are allowed to use.
Serberus provides preview-first CSV imports for customers and historical invoices, with automatic and required manual mapping, validation warnings and organization-safe matching. Permission-gated exports cover a broader set of operational records.
Owner controlRules and results stay visible✓
01Preview-first customer and historical-invoice imports02Automatic mapping plus required manual mapping03Warnings, errors and organization-safe matching04Permission-gated CSV exports across key records
What is already in the product
The details that make the workflow useful in real operations.
Import customers
Bring supported customer CSV data into the organization after the field mapping is confirmed.
Import historical invoices
Supported historical invoice rows can be validated and matched to organization records during import.
Resolve required fields
Automatic mapping handles recognized columns, while required unknown columns stay visible for manual mapping.
Act on warnings and errors
Row-level validation helps the user correct data rather than treating every parsed row as valid.
Export permitted records
Authorized users can export supported customer, job, invoice, quote, technician, time, vehicle, agreement, expense and project data as CSV.
How the handoff works
Your rules define the guardrails. Serberus carries the routine work.
Every major workflow answers the same five questions: what starts it, which rules apply, what Serberus completes, when it asks, and where the result remains visible.
Trigger
An authorized user uploads a supported CSV or requests an available export.
Rules
You confirm permissions, field mapping, organization matching and which validation issues must be resolved.
Serberus does
Serberus prepares the preview or the permitted CSV output without hiding row-level problems.
When it asks
It asks before committing an import and whenever a required mapping or invalid row needs a decision.
Where you see it
See import warnings and results in the import flow, or receive the generated export from the relevant tool.
From office to field
The context travels with the work.
The same request, schedule, customer details, photos, notes, status, and next action stay available as work moves from the office to the site.
Real product screen
Built into Serberus, not staged for the website.
This image comes from the current Serberus application. Interface details may evolve, but the workflow shown here is part of the product surface audited for this site.
Serberus
Put the handoffs somewhere dependable.
Serberus does the heavy lifting, brings the exceptions back to you, and keeps the result visible.