BookingKoala / CSV migration

Move the records. Keep the audit trail.

Miasbooking imports customers and individual jobs through a reviewable CSV workflow. Nothing is written until the owner reviews a dry run and confirms the exact plan.

1

Export

Export customers and individual visits from BookingKoala or another system as CSV.

2

Map + dry run

Adjust source-column mapping and review every valid, skipped, warning, and exception row.

3

Commit

The server recalculates the plan under a tenant lock, then writes the approved batch atomically.

4

Reconcile

Download source and destination counts plus the row ledger before operating from Miasbooking.

Supported today

One source row, one reviewable outcome

  • Booking ID, customer name, email, phone, and service address
  • Service, frequency, service date, requested time, and job total
  • Pending, confirmed, completed, or canceled job status
  • Unpaid, partial, paid, or waived payment status
  • Customer-only rows as leads when no job fields are present
Safety rules

No silent customer contact or duplicate flood

  • Imports never send customer email, SMS, invoices, or review requests.
  • Booking IDs—or email + date + time—make reruns idempotent.
  • Every batch is pinned to one workspace and cannot read or write another tenant.
  • Exceptions and reconciliation reports remain downloadable after rollback.

What migration does not do

CSV migration creates individual historical or future visits. It does not silently create a new recurring series, copy saved cards, reproduce every vendor-specific automation, or promise a field that was not exported. After reconciliation, the owner intentionally starts any future repeating schedule in Miasbooking.

Rollback also stops safely if an imported booking or lead was edited or gained operational history. That prevents a cleanup button from erasing work performed after import.

Private beta migration

Test a representative file before committing.

Start with a small export that contains your real service names, frequencies, statuses, and customer-only rows. Keep the source system available through reconciliation.