Switch · Partial
PartialSwitch without promising magic one-click from every legacy tool
Migration is the hidden cost of shop software. Workshop Wrench provides an import path for operational data — Partial honesty: design-partner quality, not a certified MechanicDesk/Shopmonkey one-click claim.
Primary persona: Owner / office manager
The problem
What breaks without this process
Shops stay on bad tools because re-keying 10 years of customers feels impossible.
Why it matters
Rationale — profit, risk, and shop floor truth
- 01
Customers/vehicles/parts are the day-one entities that unblock go-live.
- 02
Accounting history should stay in Xero/MYOB — do not force GL migration myths.
- 03
Parallel-run week on the board beats big-bang cutovers.
Proof from the live demo
Real UI — not a pitch mockup
Captured from the seeded multi-tenant demo. Open the same surface with demo credentials.
Stage sequence
Step-by-step use case
Each stage lists the action, the business why, and the intended outcome. This is how we implement and test the product — not marketing fiction.
- 01
Export legacy CSVs
Action
Pull customers, vehicles, parts from current system.
Why this stage
Clean inputs beat messy imports.
Surface: Legacy systemOutcome: Files ready - 02
Run import wizard
Action
Map columns and import into tenant.
Why this stage
Operational data lands in CRM/parts.
Surface: /importOutcome: Rows loaded - 03
Parallel week
Action
Run board on Wrench while legacy remains read-only backup.
Why this stage
Risk control for go-live.
Surface: BoardOutcome: Confidence
Related search intent
- migrate shop software
- import customers workshop
- switch garage software