Corvin help

Bringing your old system across

The reason most shops never switch is that their customers, history and unpaid invoices live somewhere else. Move them first, and you only run one system.

Where it lives

Settings → Data → Move your data across

The wizard takes one CSV per list. Export from Jobber, Housecall Pro, ServiceTitan, QuickBooks or Epicor as they come, or from a spreadsheet you keep yourself — you do not need to reshape the columns first, because you tell Corvin what each one means.

Upload in this order

Each list can depend on the one above it, so an invoice can find its customer. The wizard offers them in order and says what each one needs first.

  1. Customers
  2. Crew
  3. Parts
  4. Jobs needs customers
  5. Quotes needs customers
  6. Quote lines needs quotes
  7. Invoices needs customers
  8. Invoice lines needs invoices
  9. Payments needs invoices

Nothing is written until you say so

  1. Upload. The file is stored exactly as exported, headers and all, so you can see what you gave it.
  2. Map. Match your columns to Corvin's fields. Familiar exports are matched for you; anything unrecognised waits for you to say what it is.
  3. Preview. Corvin shows exactly how many rows will land, which will be skipped, and why. Rows that cannot be read — a date that is not a date, a customer that does not exist — are listed individually rather than failing the file.
  4. Import. Only now does anything get written. Fix the rows it refused and run it again; applying a file twice does not create the records twice.

What it does with messy data

Exports are rarely clean, so the importer is deliberate about the cases that bite:

  • Money comes in as $1,234.50, 1 234,50 or (75.00) for a credit, and all of it is read as a number.
  • Dates are read American-first, because these exports overwhelmingly are — except where the first number is above twelve and can only be a day. A date that cannot exist either way is refused rather than quietly shifted.
  • Statuses are translated into Corvin's words where we recognise them. One we do not recognise is kept as written, so you can see it and fix it; a wrong status is worse than an unfamiliar one.
  • Your numbering survives. Job, quote and invoice numbers come across as they were, because those are what you search by and what your customers quote back at you.

Undo

Every batch can be reversed. Undo import removes exactly the records that batch created and nothing else. Anything you have since built on — an invoice raised against an imported customer, say — is left in place and told to you, rather than cascading through a week of real work. After an undo the file is ready again, so you can fix the mapping and re-run it.

Removing a batch from the list is not an undo. That clears the file and its history; the records it created stay.

What does not come across

  • Time punches and old timer sessions. Keep the old system's payroll reports; start the clock fresh here.
  • Attachments and photos. Most systems do not export them in a form that can be re-attached to the right job.
  • Recurring schedules. These are rebuilt in Corvin rather than imported — the recurrence rules rarely translate, and rebuilding a maintenance round takes minutes. See Work that repeats.

We import from exported files rather than logging into your old account. A CSV export works today and needs nobody's permission but yours.

Export you cannot make sense of?

Send us the file with the customer details removed and tell us which system it came from. Mappings we add help everyone else leaving the same product.

support@runcorvin.com