Retail
Import a product with variants and a stock position for two locations. Sell the intended variant, review the payment and verify the resulting stock. Include a return before accepting the setup.
Retail workflowSquare to SABSUS
Move the business.
Keep the context.
Bring products, customer relationships and daily work into SABSUS with a defined migration scope. Start with a reviewed data sample and one complete workflow, then move the parts of the business that have passed the checks.
- 1 · Agree the scopeIdentify source records, active work and record ownership.
- 2 · Map a sampleReview fields, identifiers, variants and customer matching.
- 3 · Test the workCheck the first sale, booking, stock movement and payment.
- 4 · Cut over deliberatelyReconcile totals and give the team a clear fallback.
Choose what needs to move — not just which file to upload.
| Data | What to map | What to verify |
|---|---|---|
| Catalog | Items, variants, services, categories, units, prices and option sets | Stable identifiers, separate stock identities and correct modifier choices |
| Customers | Names, contact details, relevant fields and consent information | Duplicate handling, phone formats, provenance and access permissions |
| Stock | Opening quantity by item and physical location | Count date, movements during cutover and no duplicate opening adjustment |
| Future appointments | Customer, services, employee, time zone, duration and deposit references | Preserved customer promises, capacity and outstanding balances |
| Open orders | Agreed items, fulfillment state, payment evidence and responsible team | Which system will finish each order; no duplicate collection or fulfillment |
| Historical records | The agreed archive or import scope | Searchability and required retention without replaying old transactions as new activity |
Different businesses need different first tests.
Restaurant
Start with a menu item containing modifiers. Follow it from staff or online ordering to preparation, pickup and checkout. Confirm what the kitchen receives, not just the menu name.
Restaurant workflowSalon
Choose an existing future appointment with a deposit. Check the specialist's schedule, selected services, local time and final balance. Do not send duplicate customer notifications during migration.
Booking workflowService business
Bring an accepted job that still needs work. Preserve the agreed scope, current assignee, relevant document and payment position so the next employee can continue the job.
Field service workflowA payment-provider connection is not a data migration.
SABSUS can use supported Square payment configurations. Keeping Square as a payment provider and replacing parts of the business software are separate decisions. Specify which system owns customers, stock and each open order during the transition.
Do not assume stored card credentials, active authorizations, gift-card liabilities, recurring payment mandates or historical receipts can be moved by a CSV import. Their treatment depends on the provider, consent and the agreed migration method. Never put card details or account secrets into an ordinary import file.
Understand the Square payment connectionWhat you receive from a scoped migration
The project should identify included data, a field map, sample results, reconciliation checks and the point where each workflow changes systems. Record who can approve cutover and what the team does if a critical check fails. Importing rows is only one part of that work.
Can we move everything in one click?
The scope depends on available exports, data quality, provider connections and the destination workflow. Review a sample first; there is no blanket promise to transfer every record, credential and third-party relationship automatically.
Must all locations switch at the same time?
No. A phased rollout can be planned, provided record ownership, stock movements and unfinished orders remain clear. Parallel systems need an explicit boundary, not two independent copies of the same sale.
What should we prepare?
A description of the current workflow, a representative export without unnecessary sensitive data, the locations, hardware list and examples of open orders or future bookings. Migration and assisted setup costs are agreed separately from the software plan.
Start with a representative sample.
Choose one difficult product, customer and unfinished transaction. Use them to establish the import and operating requirements before moving the full business.
Review my migration scope