Check this before you read the rest
Dragon2000 has been in this trade since 1995 and it grew up serving dealers and workshops in the same system. Vehicle sales stock, forecourt advertising and feeds out to the classified sites sit alongside the service side, and plenty of businesses use both halves without really separating them in their heads.
Youzse Garage Pro is a workshop and service product. It does not hold a sales stock list, it does not advertise vehicles for sale and it does not feed the classified portals. There is no polite way to say that which makes it smaller, so we will say it plainly instead. If a forecourt is a real part of your turnover, moving to Youzse means keeping something else for the sales side or losing it, and for a lot of readers that ends the conversation here.
If you are a workshop that happens to be on a dealer system, the rest of this page is for you. That is a common position after thirty years of one supplier, and the move is straightforward once the sales question is settled.
With that out of the way, the thing garage owners actually fear about switching is not the diary and not the invoices. It is the vehicles. Years of registrations, the service history hanging off them and the MOT dates that bring the work back. This page covers what comes out of Dragon2000, what the Youzse importer reads, what does not travel, what breaks on the day and last of all the MOT reminder handover, which is the step that costs money if you get it wrong.
What moves and what stays behind
| Comes across | What to watch | |
|---|---|---|
| Customer records | Names, email addresses, phone numbers, addresses and notes | There is no named column profile for Dragon2000, so you match the columns yourself on the mapping screen and confirm every pairing before anything is written |
| Trade accounts | Company name, registration number, VAT number, address, phone and email, imported as companies | Bring the companies in before their contacts so each person attaches to an account that already exists |
| Service vehicles | Not as a file. You add each one by its registration | The plate lookup fills make, model, colour, year, fuel type and engine size, so the only thing you need out of Dragon2000 is registration against customer |
| MOT due dates | Read from the registration along with MOT status and test history | The due date Youzse works from comes from the plate, so it is right on day one regardless of what the old record said |
| Service history | As invoices against the customer, with numbers, dates, totals and status | The job card behind the invoice does not come. Labour lines, technician notes and parts fitted to a specific job stay in Dragon2000 |
| Sales stock | No, and there is no Youzse equivalent to import it into | This is the one to settle before anything else. Youzse does not hold forecourt stock or advertise vehicles for sale |
| Website and portal feeds | No | Anything Dragon2000 is feeding to a classified site or to your own website stops when the account does. Plan that separately from the workshop move |
| Parts and stock | No | Rebuild the Youzse parts catalogue for the lines you genuinely turn over rather than recreating the whole list |
| Booked in work | As appointments with date, time, customer, service, technician and status | Appointments are the last file you import, because a booking needs its customer, its service and its technician first |
Dragon2000 asks you to request more information rather than publishing a price, so no monthly figure for it appears anywhere on this page. Nothing in this table is a claim about what Dragon2000 will hand over on any given day, so look at the export you actually get before you plan around it.
What the Youzse importer reads
Youzse imports customers, companies, services, staff, appointments, quotes and invoices from spreadsheets. Each file runs the same four steps: read the file, match the columns, preview the result and commit the batch. Duplicate checking happens before the write so an existing customer is not created twice, and a committed batch can be rolled back whole.
There is no named column profile for Dragon2000, so you match the columns yourself. Youzse reads your headings, guesses the pairings it recognises and shows you every guess to confirm or change. It is a few minutes on a customer file and it is the same screen every other source uses. It is not a one click import and we are not going to describe it as one.
Vehicles sit outside all of that. There is no vehicle import in Youzse and there does not need to be, because typing a registration fills the make, the model, the colour, the year, the fuel type, the engine size, the MOT status, the next due date and the test history. The record then follows the registration if the car changes hands, which is the one thing a workshop actually wants from a vehicle record and the one thing an export could never have given you.
What breaks on the day, and what to do about it
Booked in jobs are the visible failure. Import the appointment file so the board is populated, then walk the next fortnight by eye against a printout from Dragon2000. A car arriving on a day nobody has a record of is the only part of this move a customer ever sees.
Parts on order are the quiet one. A purchase order raised in the old system means nothing to Youzse, so the part lands with nothing to book it against. Stop raising new orders in Dragon2000 a fortnight before the switch and keep a written list of the open ones by the counter.
Courtesy cars have no record type in Youzse. Block the car out in the diary as a booking against its own registration and it behaves like any other job on the board. A workaround, said out loud rather than discovered later.
And on cards, Youzse is 2.5% plus 35p per transaction with our platform fee inside that single rate. Dragon2000 publishes no card rate, so there is no published comparison to make and your own merchant statements are the only place to find the answer.
Your switching checklist
- Settle the sales question first. If you sell cars, decide what happens to stock, advertising and portal feeds before you plan the workshop move at all
- Export customers, trade accounts, service history and invoices while the Dragon2000 account is still live
- Pull one list of registration against customer, sorted by MOT due date with the soonest first
- Screenshot reminder wording and timings, labour rates, vehicle health check sheets and document layouts
- Note every open purchase order and the parts already paid for but not yet fitted
- Start the Youzse trial, which runs 30 days with no card, and import companies, then customers
- Add vehicles by registration in due date order, everything due in the next three months first
- Import services, then staff, then invoices, then booked in work
- Overlap the MOT reminders for a full cycle before you cancel anything
The MOT reminder cutover
This is the step that costs money if it is done casually, so it gets its own section on every page in this cluster. Youzse sends an MOT reminder on the exact day a vehicle reaches a reminder stop. The first stop is a lead time you set, defaulting to 30 days and adjustable between 7 and 90, and the follow ups trail it at 14 days, 7 days and the expiry date itself. After expiry there are further notices at 1, 7 and 14 days, and nothing is ever sent twice for the same stop.
The consequence is that a vehicle which is not in Youzse on the day its stop falls receives nothing at all. There is no catch up send. Add a car three weeks before its test and the 30 day reminder has gone for that year.
So the order of work is not alphabetical and it is not by customer. Take everything due in the next three months, put those registrations in first and only then start on the long tail. Keep Dragon2000 reminding for one complete cycle on top of that. A few customers hearing twice is a small embarrassment. A month of silence across a book of vehicles is a hole in the accounts that nobody ever traces back to the software.
Third-party pricing and features on this page were last checked on 10 August 2026. Rival platforms change their plans, so check their own site before you decide.
Keep reading
Leaving Fresha without losing your client list
What comes out of Fresha, what the Youzse importer reads, what does not survive the move and what to do about the booking links you have already given out.
Switching from Booksy, step by step
A running order for moving off Booksy: what to export, what the Youzse importer maps, what your bill looks like after and which links you must change.
Leaving Treatwell and taking your data with you
Treatwell says you still own your data if you cancel and that it does not sync with other systems. What both mean in practice when you move to Youzse.