Advanced Mappings

Beyond simple and formula mappings, Precision Bridge supports advanced mapping types for more complex data transformation scenarios.

Match Mappings

Match mappings are used to translate values between source and target systems — typically for choice fields like priority, status, or category where the values differ between systems.

A match mapping defines a set of value pairs: when the source value matches a defined input, the corresponding output value is written to the target field.

Use case: Migrating a priority field where the source system uses 1, 2, 3, 4 and the target system uses Critical, High, Medium, Low.

To create a match mapping:

1. Select the target field and choose Match as the mapping type
2. Define the value pairs (source value → target value)
3. Optionally configure a default value for unmatched entries

Read the in-app tooltips for detailed configuration options.

Lookup Mappings

Lookup mappings retrieve values from related records in other tables, allowing you to pull in data that isn't directly available on the source record.

Use case: The source record contains a user sys_id reference, but you need the user's email address from the sys_user table.

To create a lookup:

1. Navigate to the Lookups tab on the Migrate Records step
2. Create a new lookup definition specifying:
   • The lookup table and connection
   • The key field to match on
   • The value field(s) to retrieve
3. Return to the Fields tab and create a Lookup mapping that references your lookup definition

ID Mappings

ID mappings use table correlations to translate record IDs between source and target systems. This is essential for maintaining reference field relationships during migration.

Use case: Migrating incidents that have an assigned_to field referencing a user record. The user's sys_id is different in the target system, so you need to map the source ID to the corresponding target ID.

To create an ID mapping:

1. Ensure a table correlation exists for the referenced table (see Table Correlations)
2. Select the target field and choose ID as the mapping type
3. Configure the mapping:
   • Source expression: The source record ID value (e.g., [assigned_to])
   • Correlation: Select the relevant table correlation
   • Target field: Choose the target field to retrieve (typically sys_id)

See existing ID mappings in your template (e.g., the assigned_to field) for working examples.

Related Documentation

• Field Mapping Basics — simple mapping types (Constant, Source Field, Procedure Variable, Mapping Variable)
• Formula Mappings — using expressions to compute field values
• Configuring Lookups — detailed guide to setting up lookup definitions
• Configuring Field Mappings — walkthrough of the Fields tab
• Why Use Table Correlations — motivation and when to use correlations (required for ID mappings)
• ID Mappings (Table Correlations) — detailed guide to ID mappings with correlations
• Chaining Correlations — when parent tables have reference fields to other parents