# Solar CRM migration: keep the whole job connected | ArcSolar

> Plan your solar CRM migration with a clear checklist. Keep customers, sites, accepted quotes and next actions connected in ArcSolar.

Canonical: https://www.arcsolar.com.au/resources/solar-crm-migration-checklist  
Last updated: 2026-10-08

Migration · By Argonix Digital · Published 2026-09-12 · Updated 2026-10-08

**Key point:** Move the customer, site, accepted offer and next action together. Start with a small pilot.

[Download the migration mapping checklist (CSV)](https://www.arcsolar.com.au/downloads/solar-crm-migration-checklist.csv)

## Move more than contacts

Move more than contacts: map sites, accepted quotes, SMS threads, call history and follow-up tasks. ArcSolar supports SMS, calls, recordings, transcripts and AI summaries; confirm which historic records your export can transfer.

Sources: [Browser calls and SMS](https://docs.arcsolar.com.au/customers/calls-sms); [CallIntelligence](https://docs.arcsolar.com.au/customers/call-intelligence)

## Agree the scope first

- Keep a secure copy of the original export.
- Map old IDs to the new records.
- Confirm which files, messages and payments can transfer.
- Choose a cutover date and a migration owner.
- Agree how to prevent duplicate records and customer messages.

Sources: [ArcSolar CRM](https://www.arcsolar.com.au/solutions/solar-crm-software); [ArcSolar sales to operations handover](https://www.arcsolar.com.au/workflows/solar-sales-to-operations-handover)

## Check these records

| Record | Keep with it |
| --- | --- |
| Customer | Correct site and original ID |
| Quote | Accepted version and acceptance evidence |
| Payment | Amount, reference and actual status |
| Job | Booking, completion and open issues |
| Follow-up | Owner, due date and contact preferences |

## Example: ten records, one useful test

Illustrative pilot: move ten opportunities, including a revised quote, a cancelled job and a customer with two sites. If every contact arrives but one accepted quote is missing, fix the mapping before importing more. Repeat the pilot to check that retries do not create duplicates.

## Know what may stay behind

Some exports omit files or message history. Confirm the transfer method before cancelling your old service. A one-click migration from Pylon, OpenSolar or PipeReply to ArcSolar is not verified.

## Bring your migration questions to us

Bring a redacted field list to an ArcSolar demo. Use the [15-task demo scorecard](https://www.arcsolar.com.au/downloads/solar-crm-demo-scorecard.csv) to record evidence, setup and ownership. Compare migration, usage and retained tools with the [total-cost worksheet](https://www.arcsolar.com.au/tools/solar-crm-cost-worksheet) before agreeing your rollout.

- [Evaluate the whole solar software stack](https://www.arcsolar.com.au/compare/solar-software-australia)
- [Define the installation handover](https://www.arcsolar.com.au/resources/solar-installation-readiness-checklist)

Sources: [ArcSolar plans and scope](https://www.arcsolar.com.au/pricing)

## Sequence the rollout

Pilot an agreed sample, reconcile record counts and ownership, train one team, then schedule the agreed cutover. Preserve the old reference map and document who resolves exceptions. Confirm the supported import process before transferring live records.

- [Prepare a field-mapping worksheet](https://www.arcsolar.com.au/resources/solar-crm-field-mapping-worksheet)

## Sources

- [ArcSolar CRM](https://www.arcsolar.com.au/solutions/solar-crm-software) (ArcSolar, checked 2026-09-12)
- [ArcSolar sales to operations handover](https://www.arcsolar.com.au/workflows/solar-sales-to-operations-handover) (ArcSolar, checked 2026-09-12)
- [ArcSolar plans and scope](https://www.arcsolar.com.au/pricing) (ArcSolar, checked 2026-09-12)
- [CallIntelligence](https://docs.arcsolar.com.au/customers/call-intelligence) (ArcSolar, checked 2026-09-12)
- [Browser calls and SMS](https://docs.arcsolar.com.au/customers/calls-sms) (ArcSolar, checked 2026-09-12)
