zingfit offers a highly effective Migrations Processing Tool for migrating data directly from MBO using their Data Export service. Even with the efficiency of the process, migrating between 2 completely different systems means the process can never be 100% accurate. The zingfit migrations team is here to help you along the way with a Data Review and constant communication. Post-migration, zingfit's support team is here to help with all system/migration questions.

We recommend keeping your MBO account open for 1 month after Launch day so you can still access reports and data you might need.

Credit Cards

Credit cards are imported along with the first data export. This means any customer credit cards added or updated between the first and second data export will not come over during migration.

Class Names

MBO provides Class Types associated with classes in the Scheduler, not Class Names. If your classes are identified by class name, these unique identifiers will not come over in the migration

Series Types in the Scheduler - MBO and zingfit use a different system for applicable Series Types in the Scheduler. After migration, studios will need to go through the Scheduler to delete/add all applicable Series Types

Customer Accounts/Contracts

MBO marks some contracts as having "No Scheduled Auto Pay." In the zingfit system, this is marked as the contract being expired so they will not come over. We have found, that for some studios, half of these series are still active while others are expired. You will need to take note based on the Data Export csv provided and comp the contract where needed.

If a studio has a contract where the first month is cheaper than later months, MBO recommends collecting a deposit from customers. These deposits come over as Store Credit in the zingfit system. Studios can track all of this credit via the Outstanding Credits report and clear credit from customer accounts where appropriate.

You will find customers have "Migration Credits" on their accounts. These will normally appear under "Expired Series." MBO provides attendance records, but does not provide which info on which series/pricing option was used to enroll in each class. Since the zingfit system needs every record of attendance to be associated with a series, zingfit uses the Migration Credit as a placeholder record. Pretty much, if a class was booked with a Migration Credit, that means, it was booked in MBO prior to migration.

Customers must reset their passwords the first time they access your site after migration

Waitlisted Customers

Waitlisted customers do not come over from MBO. The studio will need to enroll the customers in the waitlists in zingfit after final migration

If, prior to migration, your client enrolled in a class taking place post-migration, and then cancelled in the zingfit system, after migration occurred, the zingfit system will return a Migration Credit to a client. We recommend having the client use this Migration Credit before using their other credits.

MBO will send the data export on the schedule days directly to you. There will be an email containing the download link and the password. Forward these emails to your Project Coach and onbaording@zingfit.com immediately. Once we have the files, zingfit will begin the migration process. A data review will have been scheduled beforehand, but please be available to reschedule depending on when we received the data and if there are any issues during the migration.

Upon migration, all enrollments for classes booked with series/contracts purchased in MBO will look like comps in the zingfit system. This will affect attendance revenue, in addition to Instructor payroll reporting (if you do not include comps.) We recommend using a blend of MBO reporting and zingfit reporting for the first month after migration. After that point, most studios reporting levels out since clients will have been charged an autopay, and therefore be using contracts technically "purchased" in zingfit.

The busiest part of a migration is actually the week post-migration! For one thing, most new studios have a few weeks to get all studio configuration right, but migrating studios are already up and running and so they have more to do in less time. Additionally, studios have to deal with client confusion, both in regards to working with a new system, and second, if their series/contracts didn't come over into their account properly. We have found that most of the time, questions post-migration are actually system questions, and not any issues with the actual migration. Here are examples of some things studios might find themselves doing over the week post-migration.