Using CSV When No Integration Is Available
How to manually export and import data from your booking software when a direct API connection isn't available.
When to use this approach
If your booking software isn't supported by Nabu's API integrations yet, CSV import is how you get your data in. The end result is the same — financial dashboards with real data — but instead of an automatic connection, you periodically export reports from your software and upload them to Nabu manually.
This works with any platform that can export data as CSV files, including Boulevard, Mindbody, Jane App, Vagaro, Mangomint, Meevo, Square, PatientNow, and most others.
The general process
- Export reports from your booking software as CSV files
- Download Nabu's import templates from Setup (each section has its own template)
- Map your software's column names to Nabu's template columns
- Clean up formatting (dates, amounts, and other fields per the CSV Templates guide)
- Upload each file to the relevant Nabu setup section
What you'll need to export
To fully populate Nabu, you'll need these exports from your booking software:
| Export | What to include |
|---|---|
| Appointment/visit history | Date, service performed, provider name, client name, price, appointment status |
| Client list | Client name, ID, email, phone |
| Service list | Service name, price, duration, category |
| Sales/payment records | Invoice number, payment method, amount paid, date |
Most platforms have these reports under a Reports or Data Export section. If you're not sure where to find them, search your software's help center for "export appointments" or "export sales report."
Platform-specific tips
Every booking platform is different, but exports usually live in the same general area:
- Boulevard — Reports → Export or Data → Exports
- Mindbody — Reports → run the relevant report → Export to CSV
- Jane App — Reports → select the report type → Export
- Vagaro — Reports → Sales or Appointments → Export
- Square Appointments — Dashboard → Reports → Transactions → Export
If your platform isn't listed, look for a Reports menu or a Data Export option in your settings area. Most platforms that allow CSV export will have it there.
Mapping columns to Nabu's template
Your software's export will probably have different column names than Nabu's templates. For example, your platform might call it "Staff Member" where Nabu calls it provider_name, or "Service Total" where Nabu calls it price.
The mapping step is a one-time effort: open both files side by side and rename your export columns to match Nabu's template headers. Once you've done it once, you can save a mapping reference for future imports.
See CSV Templates for the full list of formatting rules (dates, amounts, required vs. optional fields).
Important limitation: CSV is a point-in-time snapshot
Unlike the Zenoti API integration, CSV import doesn't auto-update. When you upload a CSV, Nabu gets a snapshot of your data at that moment. New appointments and sales completed after the upload are not reflected until you import again.
How often you re-import depends on how current you need your data to be. Weekly imports work well for most businesses that want reasonably up-to-date dashboards. Monthly imports are acceptable if you're primarily using Nabu for period-end analysis rather than real-time tracking.
Frequently asked questions
How often do I need to re-import? It depends on how current you want your dashboards. Weekly imports keep your data fresh enough for day-to-day decisions. Monthly works if you review financials at the end of each period. There's no technical limit — you can import as often as you like.
Can I mix API and CSV for different data types? This isn't recommended. If you have an API connection for one source, using CSV for the same data type can create duplicates or conflicting records. Stick to one method per data type. If you add an API integration later, you can work with our team to reconcile any previously-imported CSV data.