Skip to main content

Target Map

The Target Map is a core element of Hopp’s mapping model. It defines how data should look in the target system, based entirely on the target system’s structure and requirements—not the source system. This separation ensures clarity, reuse, and governance throughout the migration process.

Target Map Video Explained​

Watch the short video below to learn more about Target Maps.

Key Characteristics​

  • Target-Centric Design The Target Map reflects the business logic and metadata of the target system, exposing an interface that specifies the required data for delivery.
  • Independent from Source Mapping for the target system can be created without knowledge of the source system, allowing teams to work in parallel and reuse Target Maps for future migrations.
  • Interface for Business Objects Each Target Map defines a hierarchy of Business Objects and their fields, forming the blueprint for how migrated data will be structured and validated.

Why It Matters​

  • Reusability – Build a library of Target Maps for repeated use across projects.
  • Governance – Provides full auditability of mappings, rules, and transformations.
  • Efficiency – Enables automation of code generation and validation, reducing manual effort.

How It Works​

  1. Import metadata from the target system (e.g., database schema or manual definition).
  2. Define the interface for Business Objects and their required fields.
  3. Connect with Source Maps through Hopp’s mapping interface for transformation and delivery.