Business AnalysisAdvanced

Data Mapping Generator

Create source-to-target mappings with transformation logic, validations and business rules.

Prompt

Act as a Senior Data Analyst and Business Analyst.

Create a source-to-target data-mapping specification using the information below.

Source system and fields:

{{source_data}}

Target system and fields:

{{target_data}}

Business and migration context:

{{context}}

Known transformation and validation rules:

{{known_rules}}

For every field, provide:

1. Mapping ID
2. Source System
3. Source Entity
4. Source Field
5. Source Data Type
6. Source Format
7. Target System
8. Target Entity
9. Target Field
10. Target Data Type
11. Target Format
12. Mapping Type
13. Transformation Logic
14. Validation Rules
15. Mandatory or Optional
16. Default Value
17. Lookup or Reference Data
18. Null Handling
19. Error Handling
20. Business Rule
21. Data Owner
22. Open Questions

Classify the mapping type as:

- Direct
- Transformed
- Derived
- Conditional
- Lookup
- Aggregated
- Split
- Merged
- Not Mapped

Also identify:

- Missing source fields
- Missing target fields
- Data-type conflicts
- Format inconsistencies
- Duplicate risks
- Data-quality issues
- Personally identifiable information
- Reference-data dependencies
- Unmapped mandatory target fields

Do not invent transformation logic or default values.

Mark unsupported mappings as open questions.

Return:

1. A source-to-target mapping table
2. Data-quality risks
3. Required business decisions
4. Validation and reconciliation recommendations

Replace the highlighted variables with information about your own product, feature or business objective before using the prompt.

{{source_data}}{{target_data}}{{context}}{{known_rules}}

Example in action

See how this prompt transforms a real input into a structured result.

Example input

Source system: Legacy CRM customer export Source fields: CUSTOMER_ID — Integer FIRST_NAME — Text LAST_NAME — Text EMAIL_ADDRESS — Text DATE_OF_BIRTH — DD/MM/YYYY CUSTOMER_STATUS — A, I or S COUNTRY_CODE — Two-character country code Target system: Salesforce Target fields: Account.External_ID__c — Text Contact.FirstName — Text Contact.LastName — Text Contact.Email — Email Contact.Birthdate — YYYY-MM-DD Contact.Status__c — Active, Inactive or Suspended Contact.MailingCountry — Country name Known rules: CUSTOMER_ID must remain unique. Invalid email addresses must be reported. Customer status codes require translation. Country code requires reference-data lookup.

Example output

MAP-001 Source Field: CUSTOMER_ID Source Type: Integer Target Field: Account.External_ID__c Target Type: Text Mapping Type: Transformed Transformation Logic: Convert the integer value to text without changing its value. Validation: Value must be present and unique. Mandatory: Yes Error Handling: Reject duplicate or missing identifiers. --- MAP-002 Source Field: EMAIL_ADDRESS Target Field: Contact.Email Mapping Type: Direct Validation: Validate using the target email-format rules. Null Handling: Allow null only if the business confirms that email is optional. Data-Quality Risk: Legacy values may contain spaces or invalid formats. --- MAP-003 Source Field: CUSTOMER_STATUS Target Field: Contact.Status__c Mapping Type: Lookup Transformation Logic: A → Active I → Inactive S → Suspended Open Question: How should unknown status codes be handled? --- Critical Data Risks: - Duplicate CUSTOMER_ID values - Invalid or missing email addresses - Unsupported country codes - Date conversion failures ``

Data Mapping Generator

Example in action

Tags