MappingCreator

Personas

Three distinct users come to MappingCreator with different starting knowledge, goals, and challenges. Recognizing your persona helps you choose the right entry point.

Persona 01

The Schema Architect

"I know exactly what's in the source — I just need to shape it into what the target should become."

Transforms the familiar into something new

Knows

Source schema deeply

Building

Target schema from scratch

Goal

Design a target schema by restructuring, renaming, and combining fields from a deeply familiar source.

Pain Points

Losing track of which source fields have already been mapped
Managing merges, nesting changes, and type conversions
Ensuring no source field gets accidentally forgotten

Workflow

Load source

Design target

Map fields

Iterate

Persona 02

The Integration Engineer

"I have the spec. Now I need to find where the data actually lives in the source — if it even exists."

Satisfying a contract with an unknown source

Knows

Target schema (spec)

Unfamiliar

Source schema entirely

Goal

Wire up an unfamiliar source to satisfy every field of a known target contract — hunting for the right properties along the way.

Pain Points

Source field names bear no resemblance to target names
Required data buried in unexpected nesting levels
Type mismatches that require unplanned transformations

Workflow

Start from target

Investigate source

Find matches

Map

Verify

Persona 03

The Mapping Auditor

"I inherited this mapping and have no idea what was intended — I need to reconstruct the story."

Building a mental model from scratch

Unfamiliar

Source schema

Unfamiliar

Target schema

Goal

Understand what was transformed, renamed, dropped, or restructured — then verify the mapping is correct and complete.

Pain Points

No mental model to start from — both sides are foreign
Ambiguous field names offer no clues about original intent
Design rationale is lost; only the result remains

Workflow

Read mappings

Trace source

Trace target

Model

Audit