How it worksStudio

Hopp Studio Map complex data, together.

The collaborative data mapping tool for source-to-target mapping of complex business objects. Quick for business analysts to learn, and precise enough to generate code from.

Built for the people who know the data.

Studio is designed for data-savvy business analysts. It replaces Word and Excel with one structured, consistent way of working.

Without Studio

Mapping spec v12.docxRules_final_v3.xlsxRe: Re: new field for segmentCode values (copy).xlsx

With Hopp Studio

CustomerBusiness object
CUST_NOholderId
CUST_NAMEholderName
BIRTH_DTbirthDate
Rule: names in title caseTested

One specification, read by business and IT

Productive quickly

Business analysts get up to speed fast, complex cases included.

Map what the business means

Whole business objects, not attribute by attribute, so mappings read well and reuse easily.

Rules you can test now

Test transformation and validation rules as you write them, while errors are easy to fix.

Mapped the way your business thinks.

Mapping field by field tangles fast. Studio groups fields into business objects, so a mapping reads the way the business thinks and everything flows through one layer.

CUSTOMERPARTYACCOUNTACCOUNTTRANSACTIONLEDGER ENTRYCUST_NOholderIdCUST_NAMEholderNameBIRTH_DTbirthDateSEGMENTsegmentACCT_NOaccountIdACCT_TYPEproductTypeOPEN_DTopenedOnBALANCEbalanceTXN_IDentryIdTXN_AMTamountTXN_CCYcurrencyVAL_DTvalueDate

Business objects in Studio: three objects, mapped once through Hopp and reused.

What your team gains.

No hand-coding team

Specifications turn into code automatically, and every mapping can be reused.

Easy to test

Trace a mapping issue to its source and fix it while there is still time.

A plan that holds

Business and code follow one specification: one version of the truth.

Better collaboration

One way of working, so the team stops correcting the same things twice.

Two maps, one clear picture.

Studio splits every migration into a target map and a source map, so each side stays clear, even in the largest programs.

How the data is produced

  • Built from source data descriptions and the target's requirements
  • Maps the source to the target interface
  • Translates source code values into target values
  • Exports as a structured specification for code generation in Core

What the new system needs

  • Built from the target system's requirements
  • Hides internal references and derived data
  • Carries extensive runtime validations
  • Reusable on every project to the same target system
Start with a proof of concept

Before you commit, we run Studio on your own data. It takes one to three weeks, depending on how ready your source data and rules are.

Plan a proof of concept

See Studio on your own data.

Bring a real mapping problem and we will walk through it in Studio with you.

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.