Migration Guides

Plan a Solar Software Migration

Use these planning resources to compare workflows, define a parallel run, retain source files, validate outputs, and decide what must be rebuilt before changing software.

Migration Guide

Aurora Solar → SurgePV

Review evaluation questions for moving from Aurora Solar, including project data, validation, retraining, and transition risks. Confirm actual import and onboarding support with both vendors.

Migration Guide

HelioScope → SurgePV

Review evaluation questions for moving from HelioScope, including project data, validation, retraining, and transition risks. Confirm actual import and onboarding support with both vendors.

Migration Guide

OpenSolar → SurgePV

Review evaluation questions for moving from OpenSolar, including project data, validation, retraining, and transition risks. Confirm actual import and onboarding support with both vendors.

Migration Guide

PVCase → SurgePV

Review evaluation questions for moving from PVCase, including project data, validation, retraining, and transition risks. Confirm actual import and onboarding support with both vendors.

Migration Guide

PVsyst → SurgePV

Review evaluation questions for moving from PVsyst, including project data, validation, retraining, and transition risks. Confirm actual import and onboarding support with both vendors.

Migration Guide

Solargraf → SurgePV

Review evaluation questions for moving from Solargraf, including project data, validation, retraining, and transition risks. Confirm actual import and onboarding support with both vendors.

What a responsible migration plan covers

1

Workflow and project fit

Test representative residential and commercial projects and document which specialist tools still remain necessary.

2

Data ownership and handoff

Export source files, reports, equipment selections, financial assumptions, and customer-facing documents before changing access.

3

Output validation

Run old and new workflows in parallel and have qualified reviewers reconcile design, energy, electrical, and financial outputs.

4

Training and cutover controls

Define owners, acceptance criteria, rollback steps, and the date after which new projects begin in the selected system.

Not sure where to start?

Book a guided demonstration using a representative project. Confirm data compatibility, required rebuilding, output scope, onboarding, and commercial terms before committing to a cutover.

Book a Migration Demo

Do not upload confidential customer data unless an approved data-processing arrangement is in place.

Don't see your current tool?

Book a demo to evaluate the workflow for your current tool. Import availability and the amount of project rebuilding vary by source system and data format.

Book a Demo

Choose which optional technologies SurgePV may use. Essential storage remains active for security and requested features.