Switch from HelioScope to SurgePV: Migration Guide for Solar Designers

If you’re running a solar EPC on HelioScope and consistently hitting the 10-project monthly cap, the 15 MW system size limit, or paying $1,200+/year for Energy Toolbase to model storage HelioScope can’t, you’re not alone. The teams switching to SurgePV in 2026 are doing it for one of four reasons — none of which require giving up the simulation accuracy that made HelioScope their first choice.

This guide walks through exactly why solar designers are migrating, what SurgePV does that HelioScope can’t, the side-by-side feature and pricing comparison, and a step-by-step plan to cut over without disrupting active projects.

Why HelioScope Users Are Switching

HelioScope earned its reputation through DNV GL-validated accuracy and a clean web-based interface. For mid-volume residential and small commercial work, it remains a capable tool. The teams switching aren’t doing so because the product got worse — they’re switching because their needs grew past what the product was designed for.

The four most-cited reasons:

1. The 10-project monthly cap is throttling pipeline velocity. Both Basic ($159/month) and Pro ($259/month) plans cap project creation at 10 per calendar month. For a residential team designing 30-50 systems monthly, that’s a 4-5x throughput problem. Teams either upgrade to Enterprise (custom pricing, opaque process) or split work across multiple seats — both of which inflate cost without solving the underlying workflow constraint.

2. The 15 MW hard cap forces a second tool for utility-scale. When a project exceeds 15 MW, HelioScope can’t model it. Most utility-scale developers also run PVsyst or PVCase to handle large systems, which means maintaining two component libraries, validating two simulation engines, and reconciling yield differences between platforms during financing reviews. The dual-tool stack costs $3,000-5,000/year per user beyond HelioScope itself.

3. Storage modeling requires a separate tool. HelioScope has no native battery (BESS) simulation. Teams designing commercial systems with storage typically pair it with Energy Toolbase ($1,200-2,400/year) or Homer Energy ($600-2,400/year) for time-of-use optimization, peak shaving, and self-consumption analysis. As storage attach rates climb past 30% in commercial markets, the workaround compounds.

4. The workflow ends at simulation — proposals and finance live elsewhere. HelioScope produces excellent yield reports but doesn’t generate customer-facing proposals, doesn’t model financing structures (loan, lease, PPA, cash), and doesn’t integrate with CRM. Most users export PDFs and rebuild proposals in PowerPoint, Aurora’s separate proposal tool, or third-party platforms like Solo or Sungage — adding 30-60 minutes per quote.

What SurgePV Does That HelioScope Can’t

SurgePV was built as an end-to-end solar design platform rather than a simulation-first tool. The four areas where it directly addresses HelioScope’s limits:

No project caps, no system size ceiling

SurgePV imposes no per-month project limit and no upper kW ceiling. Teams use the same workflow for a 6 kW residential rooftop and a 75 MW utility-scale ground-mount project. The design canvas, simulation engine, and reporting templates scale with the project — there’s no point at which the tool tells you to “upgrade your plan” or move to a different product.

Native battery (BESS) modeling

Battery storage is built into the simulation engine, not bolted on. SurgePV models AC-coupled and DC-coupled configurations, supports time-of-use rate optimization, peak demand shaving, and self-consumption modes, and integrates BESS economics directly into the financial model. For a commercial project, you size the array, pick the battery, set the dispatch strategy, and get a single integrated financial output — no Energy Toolbase license required.

Built-in proposals and financial modeling

The solar proposal software layer generates branded customer-facing proposals from the same design dataset — no re-entry, no PowerPoint, no separate tool. The generation and financial modeling module handles cash, loan, lease, and PPA structures with project-specific tax treatment, depreciation schedules, and ITC handling. A complete proposal — design, simulation, financial model, customer presentation — comes out of one workflow in a single platform.

Clara AI for faster design iteration

Clara AI (SurgePV’s AI design assistant) accelerates the layout phase by auto-detecting roof obstructions, suggesting optimal panel orientations, and flagging shading issues from satellite imagery before you start manual layout work. For high-volume residential teams, this cuts design time per project by 40-60% compared to manual placement workflows in HelioScope or Aurora.

Feature Comparison: HelioScope vs. SurgePV

Pricing Comparison

For a 5-person commercial EPC running 30+ projects per month with storage, the all-in HelioScope stack typically runs $25,000-40,000 annually across HelioScope + Energy Toolbase + AutoCAD + a separate proposal tool. SurgePV’s single-platform pricing for the same team usage profile is generally 30-50% lower while eliminating the integration overhead between four separate tools.

How to Migrate from HelioScope to SurgePV

Most teams complete the migration in 2-4 weeks of parallel operation. The phased approach below minimizes disruption to active proposals.

Week 1: Set up + validate workflow

• Day 1-2: Provision SurgePV seats, set company-wide defaults (billing rate templates, default racking, brand assets for proposals)
• Day 3: Import your active component library — modules, inverters, racking systems your team uses regularly. SurgePV pulls from the same manufacturer datasheets, so the matches are 1:1
• Day 4-5: Take 2-3 currently in-flight HelioScope projects and rebuild them in SurgePV. The goal isn’t to migrate completed designs — it’s to verify that the inputs (site, module, inverter, target size) produce yield estimates within 1-2% of the HelioScope baseline. They will

Week 2: Train the design team

• Day 1: Walk through SurgePV’s design canvas, simulation panel, and reporting layout. HelioScope users typically need 2-3 hours of guided onboarding
• Day 2-5: Each designer takes one new project end-to-end in SurgePV. Most teams report full productivity (parity with HelioScope speed) by end of week 2

Week 3: Run new projects in SurgePV, finish HelioScope projects in HelioScope

• All NEW project intake goes into SurgePV
• Active HelioScope projects mid-quote complete in HelioScope to avoid disrupting customer-facing timelines
• This week typically covers the longest in-flight HelioScope project’s remaining timeline

Week 4: Cut over and cancel HelioScope

• Confirm no active HelioScope projects remain
• Export project data and yield reports from HelioScope for archive (PDF + screenshots — there’s no native export format that imports into other tools)
• Cancel the HelioScope subscription
• Cancel any auxiliary subscriptions HelioScope required: Energy Toolbase, Homer Energy, AutoCAD (if no longer needed), proposal tools

When NOT to Switch from HelioScope

In the interest of being honest: HelioScope remains a strong choice for some teams. Don’t switch if:

• You design under 10 projects per month and only need yield simulation (no proposals, no storage, no financial modeling). HelioScope’s Basic tier at $159/month is cost-effective for this use case
• You’re inside the Aurora ecosystem and use HelioScope alongside Aurora’s proposal and CRM tools as an integrated stack — the per-platform handoff overhead disappears
• You only design residential systems and use Aurora Solar for proposals — the workflow integration between Aurora and HelioScope is tight enough that switching to SurgePV adds friction unless you’re also leaving Aurora

For everyone else — high-volume residential, commercial with storage, utility-scale above 15 MW, or any team paying for HelioScope plus 2+ auxiliary tools — SurgePV’s all-in-one workflow typically delivers better total economics and faster project velocity.

Common Migration Concerns

“Will I lose simulation accuracy?” No. SurgePV uses the same module-level simulation methodology underlying HelioScope’s DNV GL validation. Yield estimates between the two platforms typically differ by less than 2% for the same inputs.

“What about my historical project archive?” SurgePV doesn’t import HelioScope project files (no industry interchange format exists). Most teams keep HelioScope archives as PDF exports for compliance/historical reference, then build all new work in SurgePV. Active projects mid-quote complete in HelioScope.

“Can my designers learn SurgePV quickly?” HelioScope users typically reach productivity parity within 5-7 working days. The underlying solar concepts (string design, simulation, irradiance modeling) translate directly — the only learning curve is interface familiarity and discovering capabilities HelioScope didn’t have.

“What about Aurora projects we still need to access?” SurgePV runs alongside Aurora/HelioScope without conflict. Many teams during transition keep both subscriptions active for 30-60 days, then cancel HelioScope once the migration is complete.

Frequently Asked Questions

The questions above plus deeper coverage are answered in the FAQ schema on this page. The short version: SurgePV exists to be the platform HelioScope users wish HelioScope had become — same simulation rigor, no per-month or system-size caps, native storage, built-in proposals and financial modeling, and Clara AI to compress design time on residential work.

If you’re evaluating the switch, the fastest way to verify fit is a 20-minute demo using one of your actual project types. We’ll show the end-to-end workflow for your specific use case (residential, commercial with storage, or utility-scale) and you can compare directly against your current HelioScope process.