Migration

Moving off a labeling system you already have.

Every enterprise labeling vendor will tell you migration is straightforward. The useful conversation is about which parts are not, and who absorbs them.

Where the cost actually is.

True of moving off any labeling system, and true regardless of which vendor you move to. Price these four before you price a subscription.

Templates that have to be rebuilt.

The difference between a library that migrates and one that is recreated by hand is often the largest single line in the project, and it depends on how consistent your current templates are as much as on either vendor.

Printing workflows.

If the new system's printing model does not fit your lines, either the lines change or people work around the system. Both are expensive, and only one of them shows up in a plan.

Validation evidence.

How much of the IQ/OQ/PQ package the vendor supplies versus how much your quality team writes and executes. This varies enormously between vendors and is rarely discussed before contract.

The history you cannot delete.

Record-retention obligations usually mean audit history has to remain available after the system that created it is retired. Whether that means migrating it or keeping the old system read-only is a question with a real cost attached.

Questions to ask every vendor.

Including Innovatum. These are answerable specifically, and a vendor that answers them generally is telling you something.

  • What proportion of a template library like ours typically migrates, and what typically gets rebuilt?
  • Show us the printing workflow configured for a line like ours, not a demo line, a line like ours.
  • Which validation documents do you supply, which do we execute, and what does your validation support actually include?
  • What happens to our validated state when you ship a release, and how much notice do we get?
  • What do you recommend we do with the audit history in our current system?
  • What does adding the second site cost, in money and in revalidation?
  • Can a contract manufacturer print without joining our network?
  • What is the annual subscription, and what sits on top of it?

Questions people ask.

Can RONOVA import templates from our current labeling system?

RONOVA is built for data migration from existing label systems. What migrates cleanly and what has to be rebuilt depends on what you are moving from and how consistent your current library is, so ask for an assessment against a sample of your real templates rather than a general assurance.

How does RONOVA compare to other enterprise labeling systems?

This site does not publish feature comparisons against named products, because an accurate one requires sourced and dated information about someone else's roadmap and an inaccurate one is worse than none. What is published is RONOVA's own position in detail, including the pricing, which most vendors in this category do not publish at all: that is a comparison you can make yourself.

What happens to the audit history in our old system?

That depends on your record-retention obligations and on what the old system allows, and it is worth settling early because it can outlast the migration itself. The two usual answers are migrating the history or keeping the previous system available in a read-only state; both have a cost, and a migration plan that does not mention it is incomplete.

Will a demo use our labels?

No. Demos run on generic data and generic labels rather than your artwork or your data. What we will do is talk through how the system would work for your particular workflow and requirements, which is a more useful conversation than watching your own label appear on someone else's screen.

Cookie preferences