How do you import WinOLS projects into a file library?

Many tuners have years of work in WinOLS projects and nothing else. That work can go into your library, so File Match and your tuners can find it. The portal reads the project file directly. It does not open WinOLS and does not need it installed, and nothing changes in your projects.

How do I import them?

The same way as any other file: open AI File DB, press Batch upload and drop the project files or the folder that holds them. A large drop is split into parts automatically. The import guide has the whole sequence. Projects then appear as groups in the review, ready to check.

What does the portal read from a project?

• The images. The first image is taken as the original, by its position in the project. Later versions become tuned files.
• The names. Each version's own name is used for the work when the project's records add up.
• The car. Vehicle details stored in the project fill in the car, and the engine is taken only if it agrees with the stated power. If not, you are asked to pick it.

When do I have to tick the work myself?

When a project has several versions and their names do not say clearly what each one does. With one tuned version, the project's labels or the file name are used. With several, a person decides, because a wrong guess here could later put the wrong file on a car. Read why every tuned file must say what work it does before you skip this step.

Why would a project be refused?

Each of these comes back with its reason.

• It is too small, or it is not a project file.
• The versions inside it cannot be located.
• It holds no ECU read.
• Its memory is split into segments the reader does not handle.
• The images do not fit the project's own records.
• It holds only an original, with no tuned version. Add those as ordinary originals instead, by exporting the read.

Each image can be up to 128 MiB, and a project can hold up to 64 versions. A refused project stays in WinOLS, unharmed. Export its read and its tuned file and add them as plain files if you want them in the library.

Is a checksum corrected on import?

The portal stores the data as it finds it. Treat imported work like any old file: if it was correct when you delivered it, the data is the same now. For how WinOLS fits with a portal day to day, see our WinOLS page.

What should I do after the import?

Check the groups marked Needs review first, then commit. Then search your library for two or three cars you know well, and confirm the original and the work look right. Finally, if you plan to use File Match, try it in Simulate. How File Match decides explains what you will see.