Specification becomes code
Studio mappings become code automatically, so what runs matches what was specified.
How it worksCore
Hopp Core Your migration, running like clockwork.
Core generates the migration code from your Studio mappings and runs it. Reliable migrations, without months of hand-built development or a heavy ETL team.
Dependable at any scale.
What your team specifies in Studio becomes code automatically, and Core runs it as often and at whatever scale the migration needs.
Reliable execution
A runtime built to run generated code dependably, run after run.
Many projects at once
Parallel projects across several servers, for large and complex programs.
From your map to running code, automatically.
Hand-written rules, safely separated.
A stub for every manual rule
Until the rule is written, its placeholder reports an event, so nothing is skipped silently.
Kept in its own file
Developers write the rule in Visual Studio, in a file the generator never touches.
Room for every project.
Core runs isolated projects in tracks. One server hosts several tracks, and Core can use several servers, so large programs iterate in parallel.
Let the runs take care of themselves.
An optional PowerShell module automates the jobs you would otherwise submit by hand from Portal.
- Jobs and schedules
Parameterised jobs and schedules that restart from the point of failure.
- Part of the bigger flow
Octopus Deploy, Control-M, Automic or Tivoli can run migration jobs as steps.
- Unattended development runs
Developers script runs that take care of themselves.
Made for technical teams.
Where the migration runs
Deploy generated code, add custom transformations and run the migration, with everything from Studio at hand.
View StudioInstall and run
Download from the support site and follow the guide. Assisted and cloud-based installation are available too.
Visit the support centerSee Core run your migration.
We will show you generated code, manual rules and a live run on the Core Runtime.