News

New Hopp release: Hopp 2.7

Hopp 2.7, the latest release of our end-to-end data migration software: guided installation, mappings that survive target changes, and locked deployments.

Hopp Tech3 min read

Hopp is end-to-end software for complex data migrations. Business analysts map the data in Hopp Studio, Hopp generates the migration code from those mappings and runs it, and teams follow the results and sign off in the Hopp Portal. Hopp 2.7 is the latest release. In short:

  • Guided installation. Installers and a setup wizard in your browser replace the manual, multi-step setup.
  • Restructure without losing work. Moving an object in the Target Map keeps its identity, so the source mappings built on it follow.
  • Control who deploys. Lock a Track to authorized users, with every deployment recorded.
  • More sign-in options. Okta, Auth0 and Keycloak, as well as Microsoft Entra ID.

This post is about what the release means for your team. The release notes for Hopp 2.7 on our wiki describe every change in detail.

Up and running in less time

Every hour your team spends installing servers or editing configuration files is an hour not spent moving data. Installers and a setup wizard in your browser now replace the manual, multi-step installation, and your team can run the installers unattended to set up many servers at once.

One command now sets up or upgrades the migration databases. It checks first and changes nothing if a check fails, and a dry run lets your database administrators review the changes before anything is applied.

Once it is running, the Portal also opens faster after you sign in, especially on your first visit, because it loads its parts in parallel and downloads less.

Restructure without starting over

Target models change during a project. In Hopp Studio, the Target Map describes the system you are moving to, and the Source Map describes the data you are moving from. Moving an object in the Target Map is now a true move: the object keeps its identity, where before a move created a copy and left your source mappings behind. When the Source Map already contains the destination, the source mappings you built follow the object the next time the Source Map imports the target's structure (the Target Interface).

Govern who changes what

A Track is where a migration runs, for instance test or production. You can now lock a Track so that only authorized users can deploy to it, with every deployment recorded with the user and the time. A production Track can then accept only what your release process deploys.

Hopp 2.7 also works with more company sign-in services besides Microsoft Entra ID, including Okta, Auth0 and Keycloak.

Moving to Hopp 2.7

Who should upgrade: every team on Hopp 2.6. If you already sign in through an external identity provider, read the deployment notes before you upgrade: some configurations need a change first.

If you run an earlier 2.6 release, upgrade to 2.6.16 first. Moving to 2.7 then takes a one-time setup in which you enter your existing settings again; your users, projects and client applications are kept, and later upgrades keep your settings. The deployment notes take you through every step, and the release notes list every change.

Planning your upgrade, or want to see what Hopp 2.7 changes for your project? Talk to us.

Planning a migration like this one?

Tell us which systems you are moving from and to, and we will show you how Hopp would handle it.

Talk to us

Tell us about the migration. We usually start with the systems involved and the timeline.

Please add your name.
Please add your company.
Please add a valid email address.
A sentence or two helps us route this.
We use these details only to reply to you, as our privacy policy explains.