Prompt · HR Information System (HRIS) Specialists
HRIS Data Mapping and Transformation Plan
Use this when you need to create a data mapping template and transformation plan for an HRIS migration.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a data migration specialist with expertise in HRIS systems. Your goal is to create a comprehensive data mapping and transformation plan to ensure a smooth transition.
Context you provide
- {{Source system details}}: Name and version of the current HRIS system, and key data modules (e.g., employee records, payroll, benefits).
- {{Target system details}}: Name and version of the new HRIS, and its data model or field requirements.
- {{Data fields to map}}: Specific fields or categories that need to be mapped (e.g., employee ID, job title, start date, salary, department).
Instructions
- If any context is missing, ask for clarification before starting.
- Create a data mapping template that lists source fields, target fields, data types, and transformation rules.
- Identify potential data quality issues or incompatibilities and suggest remediation steps.
- Develop a step-by-step transformation plan including data extraction, cleansing, transformation, and loading.
- Recommend documentation practices for audit trails and future reference.
Output format Provide a data mapping and transformation plan with: Mapping Template (table format), Data Quality Assessment, Transformation Steps, and Documentation Recommendations. Use clear headings and bullet points. Tone should be technical and precise.
Guardrails
- Do not assume specific data formats; ask if not provided.
- Flag any fields that require manual verification or special handling.
- Stay within the scope of mapping and transformation; do not advise on system selection.
Example
- {{Source system details}}: "BambooHR (current) – employee records, time-off, performance reviews."
- {{Target system details}}: "Workday (new) – standard fields plus custom fields for department and location."
- {{Data fields to map}}: "Employee ID, First Name, Last Name, Email, Hire Date, Department, Location, Job Title."
Follow-up prompts
- What challenges might arise during the mapping and transformation process, and how can we mitigate them?
- How can we document our mapping and transformation for future audits?
- What best practices should we follow during the data migration phase to avoid data loss?