Going Live — A Plan You Can Copy
Moving a working garage onto new software is a project, not an install. This is the shape that works: about two weeks, the data cutover on a weekend, and go-live on a Monday with a lighter diary. Copy it, put your own dates and names against it, and drop what doesn't apply.
Days count back from go-live, so T-12 means twelve days before. A tighter timeline usually compresses the middle — not the training day, and not the cutover.
Download the plan as a Word document — the same plan with blank columns for your dates, names and ticks, so you can circulate it and track it as you go.
On this page
- Milestones
- Who needs a login, and what it costs
- Your data
- Tablets and Wi-Fi
- Setting MechIQ up
- The money setup
- Customer messages
- The website booking link
- Training day
- The cutover weekend
- Go / no-go
- Go-live day and the first week
- Workstreams to own
Milestones
| Milestone | When | Why it's there |
|---|---|---|
| Kick-off: owners agreed, data export started | T-12 | Everything else waits on the data |
| Logins created, tablets ordered | T-10 | Hardware has a delivery time you don't control |
| Website booking link requested from your web company | T-10 | A third party's queue, not yours |
| Data cleaned in the old system | T-9 to T-7 | Clean once, before it's imported twice |
| Trial import checked | T-6 | Time to find problems while they're still cheap |
| Tablets set up and tested on the workshop Wi-Fi | T-5 | Signal in the far bay is always the surprise |
| MechIQ set up: rates, VAT, job types, hours | T-5 | So training runs on real settings |
| Money setup finished | T-4 | You invoice on day one |
| Team training | T-3 | Close enough to go-live to stick |
| Final data cutover | T-2 / T-1 | Over a weekend, with the old system frozen |
| Go / no-go call | T-1 | Against written tests, not a feeling |
| Go live | T-0 | Monday, lighter diary |
Who needs a login, and what it costs
Everyone who touches a job needs their own login; shared accounts make the job history meaningless. Front-of-house, reporting and owner accounts are free. Only technicians are licensed.
Two settings on each person decide it (Team Management):
- Works on jobs — can clock on, be given a job and complete one. This is what uses a technician licence.
- Book them in the diary — gets a column on the board and adds hours to the day's capacity.
| Works on jobs | On the board | Uses a licence | |
|---|---|---|---|
| Owner or manager who never works on cars | no | no | no |
| Manager who covers jobs but isn't scheduled | yes | no | yes |
| Technician | yes | yes | yes |
The middle row is the one to get right. Someone who can pick up a job uses a licence whether or not you plan their day — leaving them unbookable does not make them free. Both settings sit on a plain Technician as well as an admin, so a senior tech who shouldn't be changing garage settings doesn't have to be made an admin just to be kept out of the diary.
If adding someone takes you past your plan's technician count, MechIQ tells you which plan that moves you to and what it costs, and asks first. See Plan & Billing.
Passwords: there are no email invites for staff. You create the account and MechIQ shows the username and password once, on screen — take a copy as you go. Leave Their password blank and MechIQ generates a one-time password the person must change at first sign-in; type one instead and it is theirs to keep, with no forced change. Creating the accounts with blank passwords and handing out the printed one-timers on the training day is the usual way; typing them is for when the person is standing beside you.
Your data
How an import works — cleaning first, what comes across, why running it twice is safe — is in Data Import. What is specific to a go-live is the timing: you import twice, and the gap between the two runs is what gives you time to find problems.
- Export and clean, T-9 to T-7. What you want out of the old system: customers, vehicles, service history, suppliers, open bookings and stock.
- Trial import, T-6. Then spot-check twenty customers and their vehicle histories against the old system. This is the step people skip and regret.
- Final import, on the cutover weekend, with the old system frozen.
- After the final import, move the cars on Unassigned vehicles (imported) (vehicles the import couldn't match to an owner) to their customers as they come in. If your books are in Sage, match your Sage accounts (Settings → Accounting → Match to my Sage accounts) before the first export.
Tablets and Wi-Fi
One tablet per bookable technician, plus a spare. Install the MechIQ app, sign each person in and label the tablet with their name.
Then walk to every bay and check the signal. The far corner of the workshop is where this goes wrong, and it is much easier to fix the week before than on the morning.
Setting MechIQ up
Do it in one sitting: the setup wizard covers garage details, region, hours, rates, team and the subscription, and finishes with a readiness checklist. Afterwards the dashboard's Finish setting up card holds the rest — job types, VHC lists, schedules, suppliers, online booking.
The money setup
This is the one most plans forget, and you invoice on day one. Before go-live:
- VAT rates and labour rates — Tax & VAT, Pricing
- Invoice number prefix, so your numbering continues sensibly (Garage Profile)
- Chart of accounts and nominal codes, and the account references your accountant uses — including the ones for walk-in sales and over-the-counter purchases (Accounting)
- How you take payment, and which bank account each method lands in (Payments)
If you have a bookkeeper, this is their workstream and they should own it. Give them a login and a deadline before the training day.
Customer messages
Set your templates before go-live (Messages → Templates): booking confirmation, appointment reminder, and the NCT/MOT reminder. This is where garage character goes — "leave your locking wheel nut on the passenger seat" belongs in the confirmation, not in a phone call the next morning.
Texts go out from MechIQ unless you have your own registered sender. A branded sender is a
registration with the telecoms regulator and takes weeks, so assume the platform sender for launch
and treat branding as a later improvement.
The website booking link
If you want customers booking online, your website company has to add the link or booking code to your site. They have their own queue, so ask at T-10 rather than the week of go-live.
Test it on a hidden page first and make three real bookings end to end. Online bookings normally arrive for front-of-house to confirm rather than dropping straight into the diary — the exception is a booking deposit: if you ask for one and the customer pays it, that booking confirms itself and needs nothing from the desk. See Online Booking.
Training day
Half a day, three days before go-live, everyone in the room:
- Morning, everyone together — the diary, job cards, clocking on and off, tablets.
- Afternoon, by role — technicians, front-of-house, admin.
- Hand out logins and have every person sign in successfully before they leave. An untested login is the commonest morning-of problem.
- Freeze new bookings in the old system from the end of that day, or keep a written list to transfer.
The cutover weekend
- Final export from the old system, final import into MechIQ.
- Transfer every future booking into the MechIQ diary.
- Check the first two days' diary against the old system, appointment by appointment.
- Switch the website's booking button over.
- Hold the go / no-go call.
Go / no-go
Decide against tests, not a feeling. Agree these in advance and go only if they all pass:
- Data spot-check signed off — twenty customers, their vehicles and their history
- Every login works, on the device that person will actually use
- Tablets connect in every bay
- A test booking from the website landed in the diary
- Monday and Tuesday's diary matches the old system exactly
- Someone is named as the person to ring on the day
Go-live day and the first week
- Book the first two days at about 80%. The slack is the training.
- Fifteen minutes at the start of each day for the first week: what went wrong yesterday, what's fixed, what's still open.
- Name a champion on the floor each day — the first person anyone asks, so questions don't all land on the owner.
- Keep read-only access to the old system for at least 30 days. You will want to look something up.
- Keep one issues list. Anything unresolved at the end of the day goes to MechIQ support rather than sitting in someone's head.
- Review at the end of week one: what's working, what needs changing, who needs more time on what.
Workstreams to own
Every line needs one name against it. Fill in the owners at kick-off — a workstream with no owner is the one that slips.
| Workstream | Done looks like | By | Owner |
|---|---|---|---|
| Users and access | Everyone has a login with the right role; licences understood | T-10 | |
| Tablets | One per bookable tech plus a spare, signed in, tested in every bay | T-5 | |
| MechIQ setup | Wizard finished; rates, hours, job types in | T-5 | |
| Money | VAT, rates, invoice prefix, accounts, payment methods | T-4 | |
| Data migration | Customers, vehicles, history, suppliers imported and spot-checked | T-1 | |
| Bookings | Every future booking in MechIQ; old system frozen | T-1 | |
| Website booking | Booking link live; test bookings land in the diary | T-1 | |
| Customer messages | Templates written and turned on | T-3 | |
| Training | Everyone trained and signed in | T-3 | |
| Stock | Parts catalogue and stock levels imported and spot-checked | T-1 |
Related: The Setup Wizard · Data Import · Team Management · Plan & Billing · Online Booking