Your Best File Library Is Already on Your Desk: Importing an ECM Titanium Archive Into Your Portal

Ask a shop that has been tuning for a decade where its most valuable asset is, and you will get an answer about the workshop, or the tools, or the people. Almost nobody says the truthful thing: it is a folder on one PC, in the map editor, holding every original that shop has ever read paired with the tune it saved on that original. Thousands of jobs. Completely solved, completely paid for, and completely unable to help with the car that arrived this morning.

That archive is not a backup. It is a match library that nobody plugged in.

Why the desktop archive is the thing that matters

A file portal earns its keep in two ways. The obvious one is order flow: a customer uploads, a tuner works, a file comes back, money moves. The less obvious one — and the one that actually changes a shop’s margin — is recognition. When a file arrives that you have already solved, the portal should know, and it should deliver from what you own instead of sending the job to a tuner and a vendor bill.

That is what AI File Match does. It fingerprints every upload, reads the software and hardware numbers out of it, and looks for the same work somewhere in your library. An exact byte match is certain. The same factory ECU read by a different tool is the tier that earns its keep, because that is the one a checksum can never see.

All of which depends on the library having something in it.

A shop starting fresh builds that library one job at a time, and the hit rate climbs slowly for a year. A shop with a desktop archive already has the library. It is just in the wrong place — on a workstation, in a format the portal has never been shown, doing nothing for the dealer waiting on a quote.

What an import actually has to get right

The naive version of this job is “copy the files across”. It does not survive contact with a real archive, for four reasons.

1. The pairing is the value, not the files

A folder of loose binaries is close to worthless for matching. An original with no tune attached tells the portal nothing about what you did; a tuned file with no original tells it nothing about what it started from. What makes a library work is the pair — this original, and the exact tune that was saved on it, with the list of what that tune changed. A desktop map editor stores that relationship. An import that loses it has thrown away the entire point.

2. Your names are yours

Across a few thousand jobs you will have written the same modification a dozen ways. EGR, EGR off, EGR delete. AdBlue, SCR, AdBlue off. Fault codes written as the code, as a description, or as both. None of that should be guessed, once per file, by software. The right way round is to collect every distinct name your archive actually uses — usually a few dozen across thousands of jobs — map that list once onto the modification list your portal already has, and then run the import. One afternoon of decisions, instead of thousands of silent assumptions you find out about later when a dealer gets the wrong option.

3. Duplicates are the rule, not the exception

The same factory calibration comes through a busy shop again and again. Storing that original once per job and not once per file is the difference between an import that fits and one that fills a disk. The same is true of the tune itself: a modification that touched a few hundred bytes does not need another few megabytes to describe it.

4. Some of it will not read, and you need to know before you commit

An archive built over ten years spans versions of the software, machines, habits and the occasional half-saved project. Some of it will not open cleanly. An import that discovers this halfway through, having already written thousands of rows into a live portal, has created a worse problem than it solved.

The order that works is: read everything first and report, decide, then import. The reading pass changes nothing at all. It produces a list — how many projects, which ones will not open and why, every vehicle description found, every modification name used. You look at that list before a single file lands in the portal. Anything unreadable is set aside with its reason, and the run carries on rather than stopping dead.

Library Import

That is the shape of the tool we built. Today it reads ECM Titanium projects. You point it at your projects folder and it reads them in place — the archive is opened read-only, and nothing in it is moved, renamed or changed. It pairs each original with the tunes saved against it, files everything by make and model so you can see what you have, and produces the package your portal takes in.

Three steps, in order: scan and report · extract and sort · hand it over. You can stop it at any point and start it again later; it picks up where it left off rather than starting over.

Once imported there is no second class of file. A job from eight years ago is fingerprinted, carries its software and hardware numbers, and is matched, gated and delivered exactly like one taken this morning — including to your dealers, if you run a network. The strict safety gates still apply: a Stage 1 file never ships to a Stage 2 request, and new, unseen work always goes to a human tuner.

The honest limits

We would rather say this here than in an email afterwards.

• Not every project will read. Archives that span many years span many versions. The scan pass exists precisely so that this is a number you see up front, not a surprise.
• An import is a project, not a button. The mapping step needs your judgement about your own names, and the reading pass needs looking at. We run it with you. It is quoted on the size of the archive.
• It will not invent history. Where a job’s vehicle cannot be resolved against the catalogue, the file still imports and still matches — matching runs on fingerprints and ECU numbers, not on how a car was named — but it lands with the description it had rather than a guessed one.
• Your files stay yours. The import lands in your portal’s own library, on your server. Nothing is shared anywhere else unless you decide it is.

Who this is for

If you are moving from a desktop-only workflow to a portal, this is the difference between launching with an empty library and launching with ten years of work already recognising files on day one. If you already run a portal and the old archive has been sitting there because nobody had time, it is the same answer.

And if your archive is small, or you started on a portal and never had a desktop pile, you do not need this at all. We would rather tell you that than sell you an import.

The rest of the matching engine — the three recognition tiers, the safety gates, the undo window and where the saving actually lands — is on the product page. If you want to know whether your own archive is worth bringing across, tell us roughly how big it is and what you tune with, and we will tell you honestly — including if the answer is no.