This guide walks you through importing a clinic from Opus Dental into Muntra using the admin backend.
Before you start
Make sure the clinic's Opus database has been restored to the SQL Server instance. Everything else can be done through the admin UI.
Step 1 — Make sure the tenant database and clinic exist
Log in to the Muntra admin backend. Go to Tenant Databases and confirm that a tenant database exists for this organization and that the clinic exists under it. If either is missing, create them before continuing.
Step 2 — Open the import form
In Tenant Databases, find the tenant database for this clinic and go to Import data.
Step 3 — Fill in the form
- Opus SQL Server database name — The exact name of the restored Opus database, e.g.
Opus2. - Destination Clinic — Select the clinic you are importing into.
- Opus price list GUID — In most cases you can leave this blank. If the form shows a warning about a missing default price list, select the correct price list from the dropdown.
Step 4 — Handle warnings
The form may show one or more warnings that need to be acknowledged before you can proceed.
- "Opus mapping is done" — Check this to confirm you are ready to proceed with the import.
- Existing patients — If the tenant database already has patients, a warning will appear. This is unusual for a first import — verify it is intentional before continuing.
- User personal ID issues — If any Opus users have missing or incorrect personal ID numbers, they will be listed here. Use the Update button next to each user to correct the ID before proceeding. Unfixed issues can cause journal entries and bookings to be linked to the wrong person.
Step 5 — Submit
Click Import data and confirm the dialog. The import runs in the background — you can track it under Previous Imports at the bottom of the page. Large databases may take a while.
Scenarios where the import page can't be used
The following situations require developer involvement.
- Multi-clinic setup — If a single Opus database contains data for several clinics that need to be split across separate Muntra clinics, the import page only supports one destination clinic at a time. A developer needs to run the import with a custom mapping file instead.
- Appending data after go-live — If the clinic continued using Opus after the initial import and those newer records need to be added to Muntra, this requires a separate append process that is not available in the UI.
- Importing into a database that already has active data — If the tenant database already has live patients and remittances, importing directly risks affecting existing records. The safe approach (creating a parallel database and consolidating) must be done by a developer.
