Insights - Migrating Self-Hosted IUCLID to the Cloud: A Step-by-Step Guide

Running IUCLID on your own server made sense when you started. But on-premise installations quietly accumulate cost: Java and database maintenance, manual ECHA upgrades 2–4 times a year, backup management, and the risk of falling behind the current format right before a submission deadline. Moving to managed cloud hosting removes that burden — and a clean migration loses none of your data. Here is the path we use.

Before you migrate: a quick inventory

Know what you are moving. Take stock of:

• Your current IUCLID version (and how far behind the latest ECHA release it is)
• Datasets and dossiers — substances, mixtures, templates, categories
• User accounts and roles
• Reference / background data customisations
• Any integrations (CHESAR, scripting, the IIP, in-house systems)

The migration, step by step

1. Export from your on-premise instance

IUCLID’s built-in export produces portable .i6z archives. We export your full data set — entities, dossiers, attachments, and reference data — rather than cherry-picking, so nothing is left behind.

2. Validate the export

Before anything is imported, we verify completeness and integrity: entity counts, attachment resolution, and dataset structure. This is the step that turns “we think it copied” into “we know it copied.”

3. Stand up your managed cloud environment

We provision a dedicated IUCLID environment on the latest ECHA release. Because the target is current, the import also acts as a free version upgrade — you land on the newest format instead of carrying an old one forward.

4. Import and reconcile

We import the validated archive, then reconcile against the pre-migration inventory: every substance, dossier, and user accounted for. Discrepancies are resolved before go-live, not after.

5. Verify and cut over

You log in, confirm your data looks right in a real session, and we schedule the cut-over for minimal disruption. The old server can stay read-only as a safety net until you are confident.

What you stop worrying about afterwards

Once you are hosted, the recurring pain disappears:

• No manual upgrades — your environment tracks the ECHA release cycle (typically within a few days).
• No Java/DB maintenance — there is nothing to install or patch on your side.
• Automated backups and disaster recovery — handled by the platform.
• Access from anywhere through the browser — no VPN or local install.

And because IUCLID, CHESAR, QSAR Toolbox, and the IIP run in the same integrated environment on 4chems.com, data flows between them without manual file transfers.

A note on data ownership

Migrating does not change who owns your data. You remain the data controller; we act solely as a GDPR data processor, on EU-based, ISO 27001-certified infrastructure. You can export or permanently delete everything on request or at contract end.

Ready to scope your migration? Talk to an expert — we will review your current setup and map out a zero-data-loss migration plan.