The biggest reason workshop owners hesitate to switch from spreadsheets to proper software isn't cost or features - it's fear of the transition. "What if we lose data?" "What if my team won't use it?" "We can't afford downtime during the switch."
These are legitimate concerns. But the reality of onboarding is far less dramatic than most people expect. We've helped workshops of all sizes make the switch - from two-person operations to businesses with 130+ users across five branches. The process follows the same pattern every time. Here's what it actually looks like, week by week.
In this guide
Before You Start: What to Prepare
You don't need much. Most workshops overthink the preparation stage, assuming they need to have everything perfectly organised before they can begin. In reality, the onboarding process itself helps you organise things. Here's what's genuinely useful to have ready:
Your current customer list
Even if it's just names and phone numbers in a spreadsheet. It doesn't need to be perfect.
Your production stages
The steps an order goes through in your workshop - cutting, edging, assembly, finishing, packing, or whatever your specific process looks like.
Your team members and their roles
Who needs access, and what they need to see - office staff, shop floor workers, drivers.
Any active orders you want to migrate
Only the ones currently in progress. You don't need historical data.
Your accounting software details
For integration with Xero, Sage, QuickBooks, or whichever platform you use.
What you don't need: years of historical data, a perfect process map, or everyone to be "ready." Waiting for the perfect moment is the most common reason workshops delay switching - and as we covered in our spreadsheets vs workshop software breakdown, there is no quiet period in manufacturing. The best time to start is now.
Week 1: Setup and Configuration
The first week is about getting the system configured to match how your workshop actually operates. This is where most people expect weeks of painful setup - and are surprised by how quickly it goes.
Account setup and basic configuration
Company details, branding, currency, and preferences. This takes about 30 minutes. It's filling in a form, not a technical project.
Define your production stages
Cutting, edging, assembly, finishing, QC, packing - whatever matches your workshop. These become the columns on your visual production board. You can always adjust them later.
Add team members and set permissions
Invite your team, assign roles, and configure who can see what. Office staff get full access. Shop floor workers get the worker app. Drivers get the driver app.
Import or enter your customer list
Upload a CSV from your existing spreadsheet, or add customers as you create new orders. Either approach works.
Connect your accounting software
The Xero and Sage integrations take about 5 minutes. Authorise the connection, map your accounts, and invoices will sync automatically from that point forward.
Key Insight
Most workshops are entering orders into CutFlow on Day 1. The basic setup genuinely takes under an hour. You don't need to have everything perfect before you start using it - the system is designed to grow with you.
Week 2: Running in Parallel
This is the "safety net" period. You run CutFlow alongside your existing system so there's zero risk. If anything feels wrong, you can always fall back. In practice, most workshops find the new system faster than their old one within 2-3 days.
Enter new orders in CutFlow and your existing system
Yes, it's double entry for a short period. But it means you can compare outputs and build confidence that nothing is being missed.
Let shop floor staff use the worker app
This is where adoption starts. Workers tap their phone to move an order to the next production stage instead of walking to the office. Most find it intuitive immediately.
Start scheduling deliveries through the transport module
The transport module handles route planning, driver apps, and proof of delivery. Even during the parallel period, it's immediately more efficient than scribbled addresses and phone calls.
The parallel period typically lasts 1-2 weeks. Some workshops cut it short after a few days because the old system starts to feel like unnecessary extra work. That's a good sign - it means the new system is already proving its value.
Week 3-4: Full Adoption
This is where everything clicks. The old system gets retired, and CutFlow becomes the single source of truth for your entire operation.
Stop entering data in the old system
All new orders go exclusively through CutFlow. The spreadsheets stay as a reference, but they're no longer being updated.
Workshop team updating production status in real time
By now, the shop floor has the rhythm. Orders move across the production board as they progress through each stage. The office can see everything without asking.
Customers receiving automatic notifications
SMS and email updates go out automatically when orders change stage. The "Where's my order?" calls drop dramatically - often within the first few days of enabling notifications.
Delivery drivers using the driver app
GPS navigation, proof of delivery photos, and automatic customer notifications when the driver is en route. No more handwritten delivery sheets.
First invoices generated directly from orders
No more re-typing order details into your accounting software. Invoices are created from the order data and synced to Xero or Sage automatically.
This is the stage where workshops start wondering why they didn't switch sooner. Marecki Strefa Plyt onboarded 130+ users across 5 branches following this same approach. The scale was larger, but the process was identical: configure, run in parallel, go live.
Common Fears (And the Reality)
We hear the same concerns from almost every workshop before they switch. Here's what people worry about, and what actually happens:
"Will my team actually use it?"
Reality: Shop floor staff usually adopt fastest because the worker app is simpler than walking to the office to check a whiteboard. They tap their phone, the order moves to the next stage, and they get on with their work. It's less effort than the old way, not more. ACAS offers practical advice on managing workplace change, which can help smooth the transition if you have team members who are initially resistant.
"What if we lose data?"
Reality: Your old spreadsheets don't disappear. You can always reference them. And CutFlow backs up everything automatically. There's no moment where data exists in only one place during the transition. If you have concerns about handling customer data during migration, the ICO's guide to data protection provides clear guidance on your responsibilities. If you're still weighing the decision, our spreadsheets vs. CutFlow comparison breaks down exactly what you gain by switching.
"Can we run both systems at the same time?"
Reality: Yes, and we recommend it for the first 1-2 weeks. There's no pressure to go cold turkey. The parallel period is built into the onboarding process by design.
"What about our historical orders?"
Reality: Most workshops only migrate active orders. Historical data stays in your old system for reference. You don't need to import 5 years of orders - and trying to do so would slow down the onboarding for no practical benefit.
"How long until we see the benefit?"
Reality: Most workshops report noticeable time savings within the first week - primarily from automated customer notifications and the visual production board. The phone stops ringing with status enquiries almost immediately.
What Good Onboarding Support Looks Like
The software matters, but the support during onboarding matters just as much. The difference between a smooth transition and a frustrating one usually comes down to how the vendor handles the first few weeks. Here's what to look for:
A dedicated contact, not a ticket queue
You should have a real person who knows your setup and can answer questions directly. Not a generic support form where you wait 48 hours for a templated reply.
Screen-sharing sessions for initial setup
A 30-minute video call where someone walks you through the configuration is worth more than 30 pages of documentation. You see exactly how to set things up for your specific workshop.
Response times measured in hours, not days
During the first few weeks, questions come up constantly. If the vendor takes two days to respond, your team loses momentum and confidence. Fast responses keep the onboarding moving.
Help configuring for your specific workflow
Every workshop is slightly different. Your production stages, your delivery process, your quoting structure - the vendor should help you configure the system to match your reality, not force you into a generic template.
The vendor should understand your industry
There's a significant difference between a support team that understands bespoke manufacturing and one that only understands their own software. When you say "edging" or "nosing profile," they should know what you mean.
The transition from spreadsheets to workshop software is not the dramatic upheaval most people fear. It's a structured, low-risk process that takes 3-4 weeks from start to finish. The parallel running period means there's always a safety net. And the benefits - fewer calls, real-time visibility, automated invoicing, happier customers - start showing up within days, not months. The only regret we hear consistently is the same one: "We should have done this sooner."