The short version
Export clients from the old platform as CSV, remove duplicate header rows and obviously empty records, then use Junocal's migration wizard to map and review the data before anything is created.
Prepare the export
Export the most complete client or customer list your old platform provides. CSV is the best format because the migration wizard can inspect individual fields and show mapping issues before import.
Keep the original export unchanged as a backup.
Work from a copy if you need to clean the file.
Keep names, emails and phone numbers in separate columns when possible.
Remove report titles, totals and repeated header rows that are not client records.
Do not add passwords or payment-card data to the file.
Map and review the CSV
- 1
Open Migrate and choose the client import path.
- 2
Upload the CSV copy. Junocal reads the header row and suggests matches for common fields.
- 3
Confirm each mapping, especially first name, last name, email, phone and notes.
- 4
Review rows flagged as missing or invalid. Fix the file and upload again when a column-level cleanup is faster than correcting rows one by one.
- 5
Run the import only after the preview totals and sample records look right.
After the import
Open several client profiles and compare them with the source export.
Check international phone numbers and clients without email addresses.
Import memberships, packs or future bookings through their own migration steps rather than mixing record types into the client CSV.
Keep the original platform available as a historical reference until the migration has been reconciled.
Answers before you get stuck
Can I import client passwords or card details?
No. Do not place passwords or payment-card data in a CSV. Clients authenticate through Junocal's own secure flow, and payment details remain with the payment processor.
Should memberships and bookings go in the client CSV?
No. Import clients first, then use the dedicated migration step for each supported record type so Junocal can validate the correct fields and relationships.
Did this guide solve the problem?
Make the change, or ask with your account attached
Open the relevant Junocal screen now. If your question depends on a particular client, payment or class, Juno can send it to the support inbox with the page and studio context included.