Enterprise DNA

Instead of Keyloop DMS

Keyloop DMS comes on a private quote, through a distributor. Own your dealer management system.

Enterprise DNA builds your version around how your yard, sales desk and workshop actually run, brings your Keyloop records across, and runs it for you. One setup fee, then a monthly retainer, and the record stays in a database you own.

Keyloop publishes no price for its dealer management system. Its site asks you to talk to sales, and in New Zealand and Australia the Autoline line is sold and supported by a local distribution partner.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What sits behind a Keyloop quote

One vendor's platform holding every department's record

Keyloop sells a system that puts sales, service, parts and accounting together, with an open API layer for approved partner apps. It shows no price online and points buyers to a contact form. Here, it reaches dealers through a distributor in Auckland. Before you renew, it helps to see what the quote is really paying for.

paid

A price you only see after a sales conversation

No licence fee, module price or contract length appears on Keyloop's pages. Comparing it with anything else means asking for a written quote with each part listed on its own line.

hub

Sold and supported by a third party here

Keyloop's own region list has no Oceania option. Its distribution partner page names an Auckland company as the Autoline distributor for New Zealand and Australia, handling local sales and support.

extension

Partner apps through an approved channel

Keyloop's open API layer connects your dealership data to applications from manufacturers and partners it has approved and onboarded.

account_balance

The ledger inside the dealer system

Keyloop lists single ledger accounting as part of the system. That keeps the books close to the deals, and it also means leaving takes planning about which financial history moves and which stays for reference.

layers

A product line that is changing shape

Keyloop says it is moving from a dealer management system to an automotive retail platform, with separate sales, service, vehicle and acquisition hubs, and notes that what is available varies by region.

download

No published way to take everything out

The pages opened describe data shared with approved applications, not a full export of customers, vehicles, deals, repair orders and parts. A switch starts with asking your distributor for that extract in writing.

What you get instead

Every department's record, owned by the dealership

The yard

Stock you can question, unit by unit

Each vehicle carries its days on the lot, the reconditioning spent on it, the floorplan interest it has run up and its compliance paper.

  • check Ask what the oldest units have cost you so far and get a number per car
  • check The Consumer Information Notice, PPSR search and WoF shown together, with any gap flagged
  • check A unit cannot be stocked in without an odometer reading on record
  • check Aged stock comes up with a price-it or send-it-to-auction call

The desk

Deals that stop when the paperwork is missing

The steps from quote to delivery check the rules at the moment they matter, and name the rule they apply.

  • check No deposit on a used car without a Consumer Information Notice on record
  • check No delivery without a PPSR search, and never with a security interest still registered
  • check Large cash payments refused in line with New Zealand's ban on cash for car sales
  • check Every lost deal keeps who lost it and why, so last quarter can be reviewed honestly

The workshop

Jobs closed, billed and signed off properly

Customer repair orders and internal reconditioning sit on one list, and reconditioning cost lands on the car, not on an invoice.

  • check WoF work only booked to a technician whose inspector authorisation is current
  • check A repair order cannot close without work notes on it
  • check Finished jobs with no invoice are listed before they turn into write-offs
  • check Past buyers who have not been back for a service are listed with a phone number

Yours

Your rules, your paperwork, no distributor in between

Settings, documents and reports change when you ask for them, not when the next release arrives.

  • check Your aged-stock line, floorplan rate and service reminder window changed in one line
  • check Consumer Information Notices, sale agreements and service histories produced under your own brand
  • check Any tool can read the records, with no approval process to reach your own data
  • check Your books stay with your accountant, with one export handing deals and invoices across

Make it yours

Design your own Keyloop DMS replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Keyloop DMS. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Keyloop DMS replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Keyloop DMS data across and run it for you.

Switching

How to switch from Keyloop DMS

A move usually involves requesting the records Keyloop will release, mapping its export to the new database, checking the results and running both systems side by side before you switch.

  1. 1

    Request your records

    Ask Keyloop or your local distributor in writing what your account can export. Request customers, vehicles, deals, repair orders, parts and invoices, plus any history you need to keep. Keyloop's public information does not document a full export, so confirm what is available and in what format. Export what your account allows, and check the formats with Keyloop.

  2. 2

    Load a test run

    The included importer reads CSV files in its documented column layout. A Keyloop export has its own columns, so those fields need to be mapped before they can be loaded. Run a test first, then review the results before accepting the import. You can map the fields yourself or have Enterprise DNA handle the mapping and test run.

  3. 3

    Review what gets flagged

    Check the import report for rows it could not bring across, and review each skipped record before proceeding. Confirm that customer, vehicle and transaction details match your Keyloop records. Imported vehicles start without a CIN or PPSR recorded, so verify that paperwork as part of bringing each unit into the new system. Do not assume a missing value means the paperwork was never completed.

  4. 4

    Run both systems side by side

    Keep Keyloop available while you use the new database for a short, agreed period. Compare key records and make sure your team can find the customers, vehicles, deals, repair orders, parts and invoices they need. Reconcile any differences and resolve import or process issues before relying on the new system. Keep your accountant involved in the handoff for ledger information.

  5. 5

    Switch off Keyloop DMS

    Turn off Keyloop only after you have checked the imported records, reconciled the information you need and confirmed that the new process works for your team. If your business depends on manufacturer or finance connections, confirm those requirements have been reviewed and scoped before cutover. The included version does not provide manufacturer connections, and the general ledger stays with your accounting system.

construction

Where the real effort goes

The main work is usually mapping Keyloop's column names and your own fields and rules, then deciding how much history to bring across. Some information may need checking or handling separately, especially accounting records and required connections. The importer reports rows it skips, and imported vehicles start without CIN or PPSR on record. If Enterprise DNA runs the migration, it handles the field mapping and test run.

Not ready for a call?

Get your Keyloop DMS switch plan by email

We will send you the step-by-step plan for moving your business off Keyloop DMS, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways off Keyloop

Try the free version, have your own built, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo from GitHub
  2. 2 Run npm run demo, then open the folder in Claude Code
  3. 3 Ask what needs attention on the yard, the desk and in the workshop
  4. 4 Map your Keyloop customer and vehicle exports into the CSV columns the included importer expects
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check We ask for the Keyloop extract you are entitled to and map customers, vehicles, deals, repair orders and parts
  • check Your approval steps, aged-stock rules, documents and reports written around how you work
  • check The move of your ledger planned with your accountant and the accounting system you use next
  • check Manufacturer and finance connections scoped where a franchise depends on them
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and run inside Omni by Enterprise DNA alongside the rest of your business
  • check Access for sales, service and parts staff, and backups, set up and kept
  • check A morning list of what needs attention ready before the doors open
  • check New sites and reports added without a new quote from a distributor
Book a discovery call

Questions

Instead of Keyloop DMS, answered

How much does Keyloop DMS cost? expand_more

Keyloop does not publish a price. Its website sends buyers to a contact form, and in New Zealand and Australia the Autoline line is sold through a local distributor. Ask for the licence, each module, implementation, training and any partner connections to be priced separately before you compare it with anything.

Can we get our records out of Keyloop DMS? expand_more

Keyloop's pages talk about sharing data with approved partner applications, not about a full export. Ask your distributor in writing for customers, vehicles, deals, repair orders, parts and invoices, plus any history you must keep. Enterprise DNA maps what comes back and does a test run before anything is accepted.

Does the free version import Keyloop data directly? expand_more

No. The included importer reads CSV files in the column layout it documents. A Keyloop export has its own columns, so you either map them yourself or have Enterprise DNA map them, check what carries across and what does not, and reconcile the result before you switch.

What happens to the accounting Keyloop holds? expand_more

The free version keeps the dealership's operating record but is not a general ledger. Your books move to an accounting system built for that, with deals, invoices and parts handed across by export. Enterprise DNA plans the cutover with your accountant so nothing in the ledger is left hanging.

We are a franchise dealer. What about the manufacturer connections? expand_more

The free version has no manufacturer connections. When Enterprise DNA builds your version, the first review lists which manufacturer and finance links each site cannot work without, and those are scoped into the build before anything is switched off.

Hold your dealership record yourself

Spend 30 minutes with Sam going through your Keyloop quote, who uses which part of it, the manufacturer and partner connections each site relies on, and what your distributor can export. You will leave knowing whether an owned version fits. If it does, Enterprise DNA builds and runs it. If not, you keep the comparison and the free version.

Dealership for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Keyloop DMS?

Get your version built