Map data fields between two systems for an integration
A field-by-field mapping spec with transformations, sync rules, and error handling for connecting an ERP, CRM, or spreadsheet tool.
The prompt
Help me write a data mapping specification for integrating two systems.
Source system: [e.g. our ERP, CRM, accounting system]
Target system: [e.g. Airtable or Smartsheet, a data warehouse, another app]
Records to sync: [e.g. contracts, expenses, invoices, payments, project milestones]
Source fields: [PASTE field list with types, or a sample export with headers]
Target fields or structure: [PASTE, or say "design it for me"]
Operations needed: [create / update / delete, one-way or two-way, batch or real-time]
Who needs access to what: [roles and permissions]
Volume and frequency: [records per day, how fresh the data must be]
Produce:
1. Mapping table - columns: source field, source type, target field, target type, transformation rule (format, units, currency, code lookups), required?, notes.
2. Unique keys and matching - how records are matched across systems so updates don't create duplicates.
3. Sync rules - direction, which system wins on conflict, how deletions are handled (hard delete, archive, flag).
4. Data quality checks - validation before load, what happens to rejected records, how errors are reported.
5. Permissions - who can view, edit, or trigger batch operations in the target.
6. Gaps and questions - fields with no match, ambiguous meanings, picklists that need a lookup table.
7. Test plan - sample records to test, including edge cases (nulls, special characters, very large amounts, past dates).
If I ask for code, give a short example of a batch upsert using the target system's API, with placeholders for credentials - never hard-code keys. Do not guess field meanings; list them under questions.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- e.g. our ERP, CRM, accounting system
- e.g. Airtable or Smartsheet, a data warehouse, another app
- PASTE field list with types, or a sample export with headers
- PASTE, or say "design it for me"
- roles and permissions
- records per day, how fresh the data must be
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Price and document a change order before doing extra workA change order with cost breakdown, schedule impact, and justification that the owner or GC can approve quickly.
- Prepare for a building inspection so it passes the first timeA trade-specific pre-inspection checklist and walkthrough plan that catches common failure items before the inspector arrives.
- Write SMART goals and action steps for a school improvement planTurns needs-assessment data into measurable school improvement goals, strategies, and progress checks.
- Write a sole-source justification that will survive reviewA noncompetitive procurement justification with the legal basis, market research, and price reasonableness that auditors and procurement officers expect.