Move from Mangomint to Clinvello

Treat the full transfer as its own project.

Connecting Mangomint moves selected work. Replacing it changes the records, financial obligations and daily workflows the clinic relies on. Name an administrator to own the transfer and a clinical lead to check the record archive.

Connection availability is owner-confirmed. Confirm the exact actions, account permissions and location coverage during setup.

Your transfer, step by step.

1. 01

   Inventory what lives in Mangomint

   List clients, future appointments, notes, photos, consents, inventory, packages, memberships and outstanding balances. Mark which records exist in Mangomint, which live elsewhere and who can authorize each export.

2. 02

   Export and preserve the originals

   Mangomint documents desktop client-list CSV export, subject to permissions and selected filters. This is a client-list report, not proof of a complete export of appointments, forms, messages or financial obligations.

   Keep a dated original copy in the clinic’s approved storage. Request any separate attachments or assisted exports before the current account closes.

3. 03

   Verify the destination import process

   Ask the destination provider to demonstrate an actual import from Mangomint, including supported record types and the destination location. Agree on an authorized transfer workspace before sharing files. A proposed workflow is not evidence of a working importer.

4. 04

   Map the fields and run validation

   Match patient identifiers, names, contact permissions, services, providers, dates and timezones. Ask the provider to show duplicate matches, missing fields and rejected rows. Correct the mapping before running a small trial import.

5. 05

   Reconcile records, balances and payments

   Compare record counts and representative notes, files and appointments with the originals. Reconcile memberships, credits and outstanding balances separately. Saved cards require the payment processor’s approved process; do not put card details in the data upload.

6. 06

   Approve the cutover and keep a recovery path

   Choose the final export window and stop conflicting edits during reconciliation. Approve the validated transfer, assign reminders and booking to one system, then monitor the first operating period. Keep the prior account and archive accessible until the clinic accepts the results.

Mangomint: what to check.

Mangomint documents Admin management of apps and integrations, with enable/disable controls. Confirm how the particular Clinvello connection is authorized and revoked; the general app documentation does not establish its read/write scope.

• Client-list export is desktop-only in the reviewed guide.
• Filters and staff permissions can restrict exported records.
• Check membership, package and account balances separately before any later system change.

Before you approve the next stage

1. Does the connection enforce our resources, durations and provider rules?
2. Which existing Flows and reminders overlap with the proposed Clinvello task?
3. How are forms, appointment history and outstanding balances preserved if we later change platforms?

Sign off on the record archive, financial reconciliation, access arrangements and rollback plan before closing the source system.

Compare Clinvello and Mangomint before deciding →

Source guidance

The links below support the source-system export and access notes. The checklist is editorial planning advice, not verified Clinvello screen instructions or evidence of a completed migration.

1. Mangomint client-list export (opens in new tab) ↗Source review · 2026-10-29
2. Mangomint app and integration administration (opens in new tab) ↗Source review · 2026-10-29

Need a smaller first step?

Connect Mangomint and move selected AI workloads →

Review all 39 features →