Migrate from Timely, Fresha, or Setmore

Open Import and Export, select Start switcher import, and choose Timely, Fresha, Setmore, or Other / CSV. Answer every provider readiness question before continuing.

In Choose data, review the provider-recommended datasets, add any specialist datasets only when you have suitable source data, and select the first file to import. This visible planned list becomes the migration completion contract: the project cannot be approved while a selected dataset is missing.

Record the source account, exact included location when the export covers one location, export preparation date, source timezone and currency, date order, required history period, and cutover time. Keep these settings consistent across every file in the project.

Preserve the untouched provider exports securely. Schedmo accepts CSV, XLS, and XLSX for self-service files up to 5 MB and 50,000 data rows; choose the correct worksheet when a workbook contains more than one.

Import in dependency order: clients, services, team members, package templates, sold packages, appointments, sales, inventory, then client notes. Dependent rows must identify existing clients, services, and team members safely.

Map each Schedmo field to a source column. When one value applies to every row, use an explicit constant instead of editing the provider export or relying on an assumed default.

Run Validate and continue. Server validation checks required fields, duplicate source records, email and phone conflicts, dependencies, timezone-aware dates, status values, money, tax, payment balance, currency, and unsupported refunds or adjustments.

Resolve every blocking issue and validate again after changing the file, worksheet, mapping, constant, or migration setting. Schedmo rejects a stale validation result.

Start the import and monitor the import log. It records queued, started, and finished times plus row numbers and messages for failures. Completed means every row was processed cleanly; Completed With Errors and Failed always require review and cannot be approved.

For corrected files, keep the same migration project. Records already imported successfully are skipped safely, while corrected versions can resolve earlier failed or conflicting rows without replaying successful records.

After all files are complete, select Reconcile and approve. Approval requires every planned dataset, exact source-row accounting, no failures or conflicts, and complete Setmore appointment coverage where applicable.

Compare source and Schedmo counts and business totals before approval: appointments by period and status, client samples, sales/tax/payment totals, package liabilities, and inventory quantities and value.

Reconnect Stripe, payment terminals, public booking links, forms, reminders, accounting integrations, and other provider-specific credentials. Saved cards, payout accounts, terminal registrations, and provider links do not transfer.

Use automatic rollback only before approval and only when the migration created new records without updating existing ones. If imported records are already in use or existing records were updated, contact migration support for a controlled restore.

Freeze changes in the old system, import and reconcile the final delta, obtain business sign-off, then approve the project before switching customer-facing traffic to Schedmo.