Mariana Tek to Junocal migration timeline (2026)

Moving studio software is a data and operations project, not a magic import button. The safest Mariana Tek-to-Junocal plan begins with a sample export and ends only after the owner has checked the destination storefront, schedule, balances and client communication.

Junocal is our product, so this is not presented as independent migration advice. It is the scope we can defend: migration help during your first 30 days, a documented dry run, and no promise that a source platform's private data model will map one-for-one before we inspect it.

The short answer

Do not schedule a cutover from a generic “five business days” claim. Use six gates:

1. obtain the relevant Mariana Tek exports;
2. send a sample for field mapping;
3. agree what imports, what needs transformation and what will be rebuilt manually;
4. run a dry import and reconcile record counts;
5. configure and test the live Junocal workflows;
6. communicate the change, freeze conflicting edits and cut over.

The elapsed time follows the files and exceptions. A clean single-location dataset is a smaller project than several locations with custom fields, overlapping memberships, future reservations and a branded app.

What the source documentation actually establishes

Mariana Tek's official Customers Summary report guide documents exportable customer fields such as customer ID, name, email, phone and join date. Its group fitness product page also describes full client profiles and data export options.

Those pages establish that useful data can be exported. They do not establish that every field, payment credential, custom workflow or historical object will import cleanly into a different product. The sample file remains the source of truth for the migration.

A safer migration sequence

1. Inventory the live business before exporting

List the objects that must still work after cutover:

• customers and contact details;
• future classes and reservations;
• active memberships and class-pack balances;
• instructors, rooms and locations;
• intake or waiver records that the studio is legally entitled to move;
• named equipment positions;
• refunds, credits or account balances that need an explicit decision;
• email and SMS consent evidence.

Do not assume “all data” means the same thing in both products. Name each required object and its owner.

2. Export a sample first

Pull a small, representative set before requesting a full migration. Include a new customer, a long-standing member, a customer with an active pack, a future booking and any edge case the team regularly handles.

Junocal should map that sample into three groups:

• supported as supplied;
• supported after a documented transformation;
• not transferable and requiring manual setup or a retained archive.

This is where a credible timeline begins.

3. Agree the boundaries in writing

Payment credentials, passwords and vendor-specific automation do not move through a normal spreadsheet. Junocal also does not currently import or recreate favourite-position memory. Named room positions can be configured, but clients explicitly choose an available position when they book.

If a field is clinically sensitive, legally regulated or needed for financial reconciliation, confirm the lawful basis, retention requirement and destination access controls before including it. A booking-system migration is not automatically an EHR migration.

4. Run a dry import and reconcile it

Import into a non-live setup, then compare source and destination counts. Check more than the total number of customers:

• active versus expired entitlements;
• remaining pack credits;
• future reservation dates and time zones;
• instructor and room assignments;
• duplicate email addresses;
• consent and intake fields;
• failed or skipped rows.

Keep the exception report. The owner should approve it before the destination becomes bookable.

5. Rebuild the workflows that are configuration, not data

Room layouts, class offerings, cancellation policies, term courses, storefront branding and email settings need product-aware review. They should not be copied by name and assumed equivalent.

For pick-a-spot, configure the active equipment positions in each room and test the public picker on a phone. Marking a position out of order removes it from new selection; Junocal does not automatically reroute an existing assignment, so staff must review affected bookings manually.

For courses, confirm the fixed dates, capacity and one upfront course price. Junocal does not currently automate course instalments, course swaps or favourite-position carry-over.

6. Test, communicate and cut over

Test at least one free booking, paid booking, class-pack booking, membership purchase, cancellation, waitlist promotion and named-position booking that the studio actually plans to use. Confirm the money reaches the connected Stripe account and the expected emails arrive.

Then tell customers what changes: the booking URL, how they access their secure manage link, whether a payment method must be re-established and which support address to use. Pick a cutover window, freeze conflicting schedule edits in the old system, complete the final agreed import and keep an export archive according to the studio's retention policy.

What does not have a universal answer

Contract and cancellation timing

Do not rely on a generic claim about Mariana Tek's standard term or notice window. Use the studio's signed order form and any current amendment. Ask the vendor to confirm the final service and data-access dates in writing.

Exact duration

The timeline depends on the source export, locations, future schedule, active products, exceptions and owner review time. Junocal's migration help is real; a five-day guarantee without those inputs is not.

Exact savings

Compare the studio's current written Mariana Tek total with the current Junocal pricing, including payment processing, add-ons, implementation costs and any period of parallel running. A quote-only vendor cannot be reduced to one universal monthly number.

The decision gate

Proceed when the dry run reconciles, the unsupported fields have an agreed treatment, the live workflows have passed end-to-end tests and the contract dates are known. Pause when any of those is still an assumption.

For the next step, see the Mariana Tek alternative, the migration playbook and the cost calculator. Send a representative export to hello@junocal.com before anyone promises a cutover date.