What happens to my Vorne V1 data when I move to V2?

What does the conversion actually do?

Data Converter rewrites Vorne V1 production records into the V2 schema. Counts, states, reasons, shifts and job boundaries are each mapped onto their V2 equivalent, so the converted records answer the same questions the originals did. It runs as data arrives rather than as an overnight batch, which is why a converted V1 line shows up in the same dashboards, in the same shapes, as the V2 line beside it.

The output is not an archive sitting off to one side. Converted V1 data behaves like V2 data everywhere the suite reads it, which is what puts the years before the upgrade and the days after it on one continuous timeline in OEE Explorer instead of in two systems nobody wants to join by hand.

Does anything get lost?

The direct answer: the conversion does not remove anything, and what it can produce is bounded by what V1 recorded in the first place. Those are two different questions and they are worth separating, because the second one is the one that actually surprises people.

On the first: the conversion reads V1 records and writes their V2 equivalents. It is a write forward, not a move, so your V1 records are still your V1 records afterwards. That makes it repeatable, and it means a conversion you are unhappy with costs you a rerun rather than your production history.

On the second: V1 history is interval-shaped, so converted V1 history is interval-shaped too. It answers job level and shift level questions in full, and it does not manufacture count detail inside an interval that the board never wrote down. Anyone who tells you a conversion recovers resolution the source never had is selling you something that cannot exist. The XL 800 page has the detail on what a V1 board records and why finer resolution only runs forward from the day you start collecting.

What comes across, field by field?

The mapping covers the parts of the record that reporting is built on:

• Counts. Good count and reject count, which together are the pieces produced, and the basis for quality reporting.
• States and reasons. The production state history with the reason code attached to each state, which is what downtime and top loss reporting reads.
• Shifts and jobs. Interval boundaries, so shift summaries and job history line up with how the plant actually ran rather than with clock hours.
• Custom fields. A V1 board carries user strings and user numbers that plants load from a PLC, an ERP or an operator entry. Those are real V1 data, and they are mapped into reporting tables where a plant needs them, so a field that mattered on the floor can be charted in Explorer instead of being stranded in a register nobody can reach.

Which custom fields matter is specific to your plant, so it is a scoping conversation rather than a checkbox. Tell us what you use them for and it goes in the plan.

One thing that is worth being blunt about, because the wording elsewhere in this industry is slippery: a V1 board did not record operator comments itself. It recorded states, reasons, counts and intervals. So there is no shelf of V1 comment history waiting to be moved across. Comments on a converted line start when the line is converted. If you have years of comments in a legacy V1 alerting system rather than on the boards, that is a different question with a different answer, and it is one to raise with us directly rather than assume either way.

What does converted V1 data gain?

Once a V1 line speaks V2, it stops being the exception in every report. On a converted device, operators annotate stops and events exactly as they do on V2 and the notes land in the same Comments Report. Reject codes feed the same quality analysis, so scrap breaks down by reason across the whole plant rather than only on the new lines. Employee punch-ins work with Work Tracker, so labor tracking covers the whole floor. Converted devices appear on the live timeline and raise the same alerts as the rest of the fleet.

That is the part people underestimate. The conversion is usually bought to protect history, and what it also does is bring the old lines into the present.

How do I check it is right?

Do not take our word for it, and do not take a summary chart for it either. Reconcile.

1. Pick a shift and a job you can still pull from the board’s own reports.
2. Pull the same period out of Explorer after conversion: good count, reject count, run time, downtime, and the reason breakdown.
3. Compare them. Differences should be explainable by a configuration difference you can name, not by a shrug.

Run that on a couple of known periods and you know whether to trust the rest. It is the same check we would run, and it is why converting one line first is the right way to start: your existing reporting keeps running beside it, so you have something to compare against.

What does a plant have to do to run it?

Four things. A list of the devices and their firmware versions, a server for the suite to run on, network reachability from that server to the boards, and a period of overlap where the old reporting and the converted reporting run side by side while you reconcile. There is no flag day and no plant-wide board replacement to schedule, because you can upgrade a line at a time and the reporting does not split while you do.

Data Converter has a free trial, so the first conversion can be a test against your own data rather than a purchase against a promise. What the server needs is on the technical specs page.

What if we are not moving yet?

Then the conversion is not the urgent part, and collection is. An XL board keeps a rolling window of production records, so history that is never collected off the board eventually rotates out and stops being convertible by anyone. If you are running V1 hardware and have not decided about V2, the page next door covers what works against the boards you own today: what software works with a Vorne XL 800.

Sources

What a V1 board records, and what it does not, comes from Vorne’s own XL documentation for V1 boards and from our work against real V1 data. The rolling window above is Vorne’s published figure for the XL data warehouse: production records for the last 1,000 shifts and 1,000 jobs, in the XL800 data sheet (opens in a new tab), accessed 14 August 2026. What our software does with that data is described from our own product pages. Vorne is a separate company and its marks are its own.