Bring the relationship across. Check the details that matter.

Start with the source

Tell us what you use today.

Name the tools you use for contacts, bookings, payment records and training. Tell us which information you need to keep working, which history you need for reference and which system is the source of truth for each record.

Source compatibility and available imports must be confirmed for your setup. A spreadsheet export is not automatically a complete migration, and we are not promising a direct connection to every platform. For the first enquiry, share the source names, approximate record counts and field headings. Do not send client files, payment details or private notes through a general contact message.

Map and review

Know where each field will go.

The planned migration process starts with a preview: map the source fields, inspect representative records and identify missing or unsupported values. A phone number, time zone, service label or note can mean different things in different systems. Resolve those differences before applying an import.

Review likely duplicates with care. Two records may belong to one person, while a shared surname or email can belong to different people. Keep a recoverable source export and agree how each duplicate will be handled. Only bring notes and personal information that you have the right to transfer and use.

Protect the commitments

Reconcile bookings and paid sessions.

Agree a clear cutover point for upcoming appointments, paid coaching periods and session-pack balances. Check remaining credits against sessions already used, reserved or cancelled under the applicable policy. Money collected in the old system should not become a second payment simply because its balance is recorded in Mako.

For example, a client bought ten sessions and used four. If two future bookings already reserve credits, the move needs to preserve the distinction between six remaining credits and four still available to reserve. This is an illustrative reconciliation example; actual pack rules and import support must be confirmed.

Training is a separate review

Check programs and history before promising continuity.

Workout programs, exercise formats and historical results require a separate compatibility check. A contact import does not prove that training history, attachments or every prescription field will transfer. Decide what can be brought across, what should remain in an archive and what needs to be rebuilt for the next agreed block.

The planned Beta Training connection also requires client choices about plan acceptance and sharing. Existing contact permission should not be treated as permission to expose private training records to a new coach connection.

Move in stages

Review a small group before inviting everyone.

Start with a manageable set of records, confirm the client details and reconcile service balances. Review the booking and client-facing experience before sending invitations. A draft invitation is not a delivered invitation, and an invitation is not an accepted coaching relationship.

Agree who checks changes that happen during the move, such as a payment, cancellation or credit redemption in the original system. Once the sample is right, decide the next group and timing. We will scope setup and any assistance with you; no universal completion time, free full migration or automatic transfer of payment mandates is promised.

Practical questions

A few things to know.