Migration
Migration that is not a restart.
If you run ROBAR today, the question is not what RONOVA can do. It is what happens to the system you are running now, on what timescale, and what it costs you in revalidation.
What carries across.
The things a ROBAR customer would otherwise have to rebuild, and the reason this is a migration rather than a fresh implementation.
Templates, master data and approval history.
The supported path carries all three across, and Innovatum handles the migration and revalidation. An existing configuration is extended rather than rebuilt from scratch, which is the difference between a migration and a re-implementation.
The control model you already run.
Change management with the reason captured, full audit history, electronic signature for 21 CFR Part 11. Familiar ground rather than a new compliance case to make.
Your process, not a new one.
Printing workflows are configured to match the production printing process you run today, so the plant floor is not the part that changes.
The relationship.
The same company, and the same people who already know your deployment. Migration between vendors means explaining your process to strangers; this does not.
What is genuinely different.
A migration page that claims nothing changes is not worth reading. These are real differences, and they are the reason the move is worth making rather than an inconvenience to be minimised.
Browser-based throughout.
Including printing. No client software at each site to install, patch and qualify, which is the change most visible to IT and to anyone maintaining a multi-site estate.
One record, many markets.
Destination-driven content resolves what each market requires from a single product record, rather than maintaining parallel label sets per market.
A subscription, and a choice of where it runs.
An annual subscription rather than a licence, and a choice of hosted cloud or private cloud. In the hosted service each customer sits in a logically isolated tenant database; a private cloud is single-tenant, which is the route if you have data residency requirements. This changes the commercial and IT shape of the system, so your own security review will want to look at it.
AI-assisted work.
Template matching, label refinement and analysis, reporting and configuration. New capability rather than a replacement for the control model around it.
Questions people ask.
Is ROBAR being discontinued?
No. ROBAR remains a supported product and Innovatum still sells it to customers who want it. RONOVA is the newer platform and is where most new deployments go, but moving is a decision you make on the merits rather than a deadline you are handed. If you need the support position for your own deployment in writing, ask Innovatum for it directly rather than planning around a date on a web page.
Do we lose our label templates and history?
No. The supported path carries across label templates, master data and approval history, and Innovatum handles the migration and revalidation rather than leaving an existing configuration to be rebuilt. Worth confirming for your own case: whether the migrated history satisfies your record-retention obligation on its own, or whether you also keep ROBAR available read-only for a period.
Do we have to revalidate?
There is revalidation work in any move between systems, and Innovatum handles it as part of the supported ROBAR path rather than leaving it with you, alongside the IQ/OQ/PQ documentation and validation support that comes with RONOVA generally. Ask what that division of labour looks like for your deployment, which documents Innovatum produces and which activities your quality team still executes.
Can we migrate one site at a time?
A phased rollout is the normal shape for multi-site deployments, so that a plant moves when its own validation window allows rather than all sites at once. Confirm the specifics for your estate with Innovatum, including what happens to sites still running ROBAR during the transition.
Read next.
Label Management
Design, approve and print labels from one controlled source, with electronic approval and a complete audit trail on every change.
Architecture
How RONOVA deploys and fits an existing stack: hosted cloud or private cloud, integrated with ERP, MES and PLM.
Destination Labeling
Market-specific language, symbols and regulatory content applied automatically by ship-to destination, from one approved template.
Why RONOVA
The six differences that matter.
Services
Migration, configuration and validation support.
Pricing
The published subscription figures.
Downtime, misprints and messy audits can cost millions.
See the PLM built to protect your regulated labeling.