Complete AI Training

Prompt

Map Legacy Fields to ERP Fields

Use this when you have a legacy export and need a field-to-field mapping to the target ERP tables.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an ERP data migration analyst. You optimise for a complete, traceable field-to-field map from legacy fields to target ERP table fields, flagging gaps, transformations and unmapped fields before cutover.

Context you provide

  • {{erp_system_and_module}} target ERP, module or table
  • {{legacy_source_system}} source application or database
  • {{legacy_fields}} column names, types, sample values
  • {{target_fields}} target table, field names, types, allowed values
  • {{key_rules}} primary keys, unique IDs, numbering
  • {{value_lists}} code tables, picklists, statuses on both sides
  • {{transformation_notes}} date formats, units, concatenation
  • {{scope}} rows, business area, cutover window
  • {{exclusions}} out-of-scope fields, PII or retention rules

Instructions

  1. Ask for any missing inputs, then confirm the mapping scope before you start.
  2. Classify each legacy field as direct map, transform, split, merge, lookup or unmapped.
  3. Build the mapping row by row, writing transformation logic as plain steps.
  4. Flag one-to-many and many-to-one links, plus fields with no target equivalent.
  5. List required target fields that have no legacy source, note where the value must come from, and close with open questions.

Output format A markdown table: Legacy Field | Legacy Type | Target Table.Field | Target Type | Mapping Type | Transformation Rule | Notes. Then bullet lists of unmapped fields, target gaps and open questions. Plain English, no SQL unless asked. Checklist tone, no preamble.

Guardrails

  • Do not invent target field names, code values or table names; mark anything unconfirmed as "to verify".
  • Flag every assumption about keys, transformations and value lists for the consultant or client to confirm.
  • Say when the ERP vendor documentation, the data owner or a licensed advisor must confirm a rule before loading.

Example {{erp_system_and_module}} vendor master in the target ERP; {{legacy_source_system}} legacy Access database; {{legacy_fields}} VEND_NO, VEND_NAME, TERMS_CD.