Windows migration

Moving from Rhinobase for Windows

The original Rhinobase Windows application and Rhinobase Next are separate software generations. Retain your functioning legacy installation and backups until a validated migration is complete.

1. Back up original records

Take a complete application and database backup, including photographs and linked files. Work from a copy, never the only active original.

2. Prepare a testing instance

Use a separately installed Rhinobase Next test environment without real patient information unless lawful controls and authorizations are in place. Evaluate migration with synthetic or lawfully de-identified records first.

3. Inspect, then dry-run

The visible Next interface includes Settings & Tools → Windows Import with Read patients locally, Inspect, Dry-run and Apply import. Inspect proposed mappings and review result counts before committing changes.

4. Back up Next before Apply

The application interface warns that an Apply operation may update patients by legacy ID and replace previously imported visit rows. Create an independent database and file backup before you use Apply.

5. Validate the migrated data

Compare representative records against the Windows source: demographics, clinical history, operative planning, clinical visits, photographs and drawings. Document discrepancies and correct them before migrating remaining data.

6. Keep an archival Windows copy

Maintain an appropriately secured archival copy for historical verification and retention obligations.