Practical checklists

Solar CRM field mapping worksheet

Map customer, site, owner and open-work fields before changing solar CRM. Download a CSV planning worksheet and check a small migration pilot.

Start with the source export

Keep a secure copy of the source export. List the record type, original ID, field meaning, proposed destination, transformation and test for each mapping. Agree the supported transfer method with the implementation team.

ArcSolar customer records keep the installation address, lead source, ownership and linked work together. Check the owner of the actual lead or opportunity; an account-owner label may mean something different in the old system.

Sources: [1][2]

Map the relationships that matter

Map the relationships that matter
RecordCheck before transfer
Customer and siteRetain source IDs; keep multiple installation sites distinct.
Lead and opportunity ownerMatch to the intended active member and role.
Quote and acceptanceKeep the issued version and its acceptance evidence linked.
PaymentPreserve reference and actual status; pending stays pending.
Conversation and next taskConfirm available history, next owner and due date.
Contact preferencesRetain the recorded preference and its source evidence.

These are planning checks. A row in the worksheet does not establish that a particular field, file or message can be imported.

Example: one customer, two sites

Illustrative mapping: the source has customer C-104 with sites S-1 and S-2. Its open battery quote belongs to S-2. Record both site references and link the quote to S-2; do not merge the addresses simply because the customer ID matches.

If “account owner” identifies a former rep, agree the replacement owner before transfer. Keep the old reference in the mapping register so the pilot reviewer can trace the decision. The downloadable CSV includes this fictional example and five other planning rows.

Check a small pilot before cutover

  • Reconcile source and destination counts by record type, with an explanation for exclusions.
  • Open a customer with multiple sites, a revised quote and unfinished work. Check the links and next owner.
  • Have the intended rep or operations member complete their permitted next step. An administrator’s view does not prove everyone has access.
  • Agree retry and duplicate handling, then resolve exceptions before expanding the migration.

Sources: [1][2]

Agree what transfers and what stays behind

This worksheet is a planning aid, not an ArcSolar import schema or upload template. Automated import coverage, supported formats and historical message or file transfers must be agreed separately. Keep source records available until the pilot and exception list are accepted.

Take the map into your migration review

Use the migration checklist to agree the pilot and cutover. For an ArcSolar walkthrough, bring redacted column names and a fictional job; confirm migration scope, plan and connected services before deciding.

Sources and review (2)

Published by ArcSolar. Examples are illustrative; product details come from the sources below. Editorial standards.

Put the workflow to work.

Review your migration map with ArcSolar

Book a demo