Migrating from Blueprint moves your patient records, appointments, financial history, and clinical documentation into Suno before your go-live date. Blueprint has the most detailed financial migration of any system we support — this guide covers exactly what is and is not migrated, and what you need to do to prepare.
How Blueprint migration works
Blueprint migrations use an automated orchestrator that runs all steps in a single sequence. Your onboarding specialist initiates and monitors the full process.
As part of migration, any test patients or billing records entered in Suno during your onboarding setup phase are removed before go-live. This is expected — only your migrated production data will remain.
Note: Staff in Suno are linked to patients, appointments, and invoices by name. All active staff must have Suno accounts set up before migration runs.
What we migrate
Staff
Names, email addresses, job titles, qualifications, NPI numbers, and active or inactive status
Default clinic assignment
Patients
Demographics — name, date of birth, sex
Contact information — mobile, home, and work phone numbers; email address; and primary address
Patient status (
Active,Inactive)Health card number
Do-not-mail, do-not-text, and do-not-email flags
Preferred provider and preferred clinic
Referral source and referring physician
Emergency contact — name, relationship, and phone numbers
Patient tags and grouping
Patient documents — files attached to a patient in Blueprint are migrated and stored against the patient in Suno
Appointments
Date, start time, end time, clinic, assigned staff, and appointment type
Appointment status, description, and notes
Schedule blocks (personal and off-time events)
Products and pricing
Product type | What is included |
Hearing aids | Manufacturer, model, retail price, cost, active status |
Batteries | Description, battery size, quantity per pack, catalog number |
Accessories | Description, category, vendor price, retail price, active status |
Services | Name, service group, retail price, active status |
Dispensed devices and accessories
Hearing aids — manufacturer, model, serial number, ear, color, and size
Purchase date, order date, received date, and delivery date
Warranty expiry, loss and damage warranty expiry, service plan name, and service plan expiry
Device status and notes; most recent active device per ear automatically flagged
Dispensed accessories — domes, receivers, earmolds, and tubes attached to a patient are migrated alongside their hearing aids
Financial records
Blueprint tracks all financial record types separately. We migrate each of the following:
Invoices — date, clinic, provider, total, and tax
Invoice status — zero-balance invoices marked
Completed; outstanding invoices markedReady to BillLine items — products and services, with price, quantity, cost, tax, discount, ear side, and serial number
Patient payments and insurance payments
Patient credits and insurance credits (migrated as adjustments)
Patient refunds and insurance refunds
Returned invoice flag
Note: If your practice uses QuickBooks, financial migration data will need to be synced to QuickBooks separately after go-live. Your onboarding specialist will coordinate this.
Clinical documentation
Journal entries migrated as chart notes — with original entry date, author, and entry type
Deleted journal entries are not migrated
Notes linked to appointments where a matching appointment date exists
Insurance policies
US policies — insurer, member ID, group number, plan name, policyholder details, copay, deductible, and estimated benefit
Canadian policies — insurer name, policy number, ID number, and insurer type
Recalls and touchpoints
Blueprint recalls are migrated as Touchpoints in Suno — including recall date, type, and patient link
Clinic stock
Clinic stock devices — manufacturer, model, serial number, color, size, status, and cost
Administrative data
Referring physicians (name, NPI, phone, and address) and referral sources
What we do not migrate
Staff passwords — every staff member will have a new account setup in Suno
System configuration — workflow settings, custom templates, and report templates
Structured audiogram records — any audiogram information in journal notes is migrated as text in chart notes
Patient photos — not migrated from Blueprint
Insurance claim submission history — ERA/EOB files and clearinghouse records
Hearing aid programming data — fitting software files (e.g., Noah files)
Custom report definitions
Test and demo data — records entered in Suno during onboarding setup are removed as part of the migration process
Email and communication history
Before you begin
Export your data from Blueprint — your onboarding specialist will provide the list of CSV files needed and guide you through the export process.
Confirm all active staff have Suno accounts — Blueprint links patients, appointments, and invoices to staff by name.
Confirm clinic names — let your specialist know if location names in Blueprint differ from what is set up in Suno.
Note any test data entered in Suno during setup — this will be removed as part of the prelaunch process.
Notify your team — staff will receive a Suno invite to set up their account; passwords do not transfer.
Still need help?
If you have questions about what will or will not be migrated from Blueprint, contact Suno Support with your clinic name and we'll be happy to help.