Data mapping

Mapping is where the business decisions of a migration are made, and it is the milestone the client signs before anything is loaded. The agent proposes field mappings and transformations from the source and target structures, you decide the ambiguous cases, and the agent produces transformed files you can inspect before the load. See Migration and cutover for what happens after sign-off.

1. Agree the scope

Tell the agent what should move, from where to where, and what success looks like. State whether you want a plan, reviewable transformed files, or a live load. The agent reuses the project’s connections, uploaded exports and discovery findings, so a short instruction is enough:

Migrate Contoso vendors and open AP from the GP database to the Intacct sandbox.
Produce transformed files for review first. Success: vendor count matches after
excluding inactive vendors with no open balance, and open AP total matches to the cent.

For a migration plan rather than execution, ask for one. The agent saves the required work as project tasks with mappings, validation, risks and cutover details in the task descriptions, and does not write to the target.

2. Review the proposed mapping

The agent inspects the source and target structures and proposes field mappings and transformations. It resolves obvious matches itself and asks you only about ambiguous business meaning, missing required values and potential data loss, for example a source field with no target or a code list that must be translated.

For a large mapping the agent presents the proposal as an artifact with source and target columns, so you can review it field by field and mark exceptions. Decisions you make are kept in the task description or the mapping artifact, so the reasoning survives the engagement.

i

Upload your firm’s mapping template before this step. The agent follows the template’s layout and conventions, and the mapping artifact becomes a deliverable the client already recognizes.

3. Resolve open questions with the client

Questions only the client can answer, such as which inactive customers to keep or how to treat a legacy dimension, go into a questionnaire the agent builds as an artifact. Share it by link; the client’s answers arrive in the project and the agent applies them to the mapping. Record each decision in the mapping artifact so the sign-off document is complete.

4. Inspect transformed files

By default the agent produces transformed files before it touches the target. It builds a saved tool that reads the source, applies the agreed transformations and validation rules, and writes the result to an Excel or CSV file you can download from the run. Rejected records go to a separate file with the reason for each.

Open the files, spot-check them against the source, and send the rejects to the client for cleanup. Ask the agent to adjust the rules and rerun. Because the transformation is a saved tool, a rerun applies exactly the same rules to the current data.

5. Mapping sign-off

When the mapping and the transformed files are right, export the mapping artifact as PDF or Word for the client’s sign-off, or ask the agent for a sign-off form the client completes by link. Mark the mapping task as done. The saved transformation tool is now the agreed contract for the load.

!

Nothing has been written to the target at this point. Reads and file generation do not need approval. The first write happens in Migration and cutover and pauses for your approval.