Map and validate migration files

Upload CSV, XLS, or XLSX up to 5 MB, 50,000 data rows, and 250 columns. For workbooks, select the worksheet containing the headings and records you intend to migrate.

Confirm the preview row count and headings. Duplicate headings, malformed CSV, empty files, unsupported formats, excessive columns, and oversized files are rejected before mapping.

Review every suggested mapping. A source column can map to one Schedmo field; required fields must be supplied before validation can succeed.

Use a constant when the same explicit value applies to every row, such as a zero tax amount, unpaid status, or a consistent payment method. Constants are recorded in the validation fingerprint and must not be used to guess unknown data.

Use source client and appointment identifiers when available. Map client email and phone for safe identity resolution; if they identify different clients, Schedmo reports a conflict instead of choosing one.

Import clients before dependent datasets. Appointments also require matching services and practitioners; sold packages require clients and package templates; client notes require an existing client.

Confirm the source timezone, date order, and currency. Server validation converts dates using the declared timezone and rejects invalid or chronologically impossible ranges.

For sales and sold packages, map the sale date, total, paid amount, status, and other required financial fields explicitly. Negative values, unknown states, currency mismatches, unbalanced totals, refunds, and adjustments are blocked.

Review every error by row number and field. Correct the source export or mapping, then run server validation again; warnings should be investigated even when they do not block import.

If the file, worksheet, mapping, constants, timezone, currency, date order, provider answers, or planned datasets change, validate again. Schedmo will not accept a stale validation fingerprint.

Start the import only when the server result says the file is ready. Keep the untouched provider export separately so support can trace any source row later.