Solar CRM field mapping worksheet

Prepare the right inputs

Create a mapping register before choosing an import method. For each source field record its meaning, intended destination, transformation, owner and validation example. Confirm supported destination fields with the implementation team.

Sources: [1][2]

A practical example

• Suggested register columns: source field; meaning; proposed destination; transformation; validation rule; unresolved question.
• Illustrative mapping: “account owner” may mean a sales rep, while the destination distinguishes lead and opportunity owners. Resolve that meaning before copying identifiers. Preserve opt-out evidence and stable source references.

Keep these boundaries clear

This is a planning worksheet, not an ArcSolar import schema. Automated import coverage, file formats and exports are not established by this guide. Agree the supported migration method and trial sample before transferring real records.

Sources: [1][2]

Put the checklist to work

Use one representative record to test the workflow before rolling it out across the team. Confirm what is supported in your plan and who owns unresolved work.

• Explore the related ArcSolar workflow →