Migration Guide

Switch from HelioScope to SurgePV

Why solar EPCs are leaving HelioScope's 10-project cap and 15 MW limit for SurgePV — full feature comparison, pricing, and step-by-step migration.

Keyur Rakholiya By Keyur Rakholiya · May 6, 2026 · 12 min

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.

Migration Insight

HelioScope users tend to be more productive on SurgePV than first-time solar software users because the underlying paradigms (string design, module-level simulation, irradiance modeling) translate directly. The learning curve isn’t relearning solar — it’s learning where the additional capabilities (BESS, financial modeling, proposals) live in the SurgePV interface.

Feature Comparison: HelioScope vs. SurgePV

CapabilityHelioScopeSurgePV
Web-based, no installation✅ Yes✅ Yes
Module-level simulation accuracy✅ DNV GL validated✅ Equivalent methodology
Project cap per month🔴 10 (Basic/Pro)✅ Unlimited
System size limit🔴 15 MW hard cap✅ No upper limit
Native battery (BESS) modeling🔴 Not included✅ AC/DC-coupled, TOU, peak shaving
Proposal generation🔴 Export only✅ Branded proposals built-in
Financial modeling (cash/loan/lease/PPA)🔴 Limited (G2: 5.2/10)✅ Full multi-structure modeling
AI-assisted design🟡 Basic auto-design✅ Clara AI roof detection + layout
SLD generation🟡 Basic (needs AutoCAD for full)✅ Built-in, no AutoCAD needed
Single-axis tracker support🟡 Enterprise only✅ All plans
Component library✅ 40,000+ modules, 10,000+ inverters✅ Comparable coverage
Topography modeling🔴 G2: 3.3/10✅ Terrain-aware design
Performance above 5 MW / 10,000 modules🟡 Reported lag✅ Optimized for scale

Pricing Comparison

TierHelioScopeSurgePV
Entry$159/month ($1,620/year) Basic, 10 project/month capCustom — no per-month project cap
Mid$259/month ($2,640/year) Pro, 10 project/month capCustom — scales with team size
EnterpriseCustom (project trackers + larger limits)Custom — utility-scale + multi-tenant
Battery modeling+ Energy Toolbase $1,200-2,400/yearIncluded
Proposals+ Aurora/Solo/Sungage external toolIncluded
Financial modeling+ External spreadsheet or PPA toolIncluded
SLD beyond basic+ AutoCAD $2,000/yearIncluded
Effective stack cost (commercial team)$5,000-8,000/year per userSingle-platform pricing

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

See How SurgePV Handles Your Workflow

20-minute live walkthrough using your real project type — residential, commercial, or utility-scale. We’ll show the design + simulation + proposal flow end to end.

Book a Demo

No commitment · 20 minutes · Live project walkthrough

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.

Frequently Asked Questions

Why are solar designers switching from HelioScope to SurgePV?
The two most cited reasons are HelioScope's 10-project-per-month cap on Basic and Pro plans, and its 15 MW hard limit on system size. High-volume EPCs hit both walls regularly — the cap forces them to delay quotes, and the size limit pushes utility-scale work to a second tool. SurgePV has no per-month project cap and no upper system size limit, which removes the workflow bottleneck. The third reason is the all-in-one workflow: HelioScope users have to leave the platform for proposals, financial modeling, and CRM, while SurgePV handles design, simulation, proposals, and financial analysis in one platform.
How does SurgePV pricing compare to HelioScope?
HelioScope is $159/month Basic ($1,620/year) or $259/month Pro ($2,640/year), with project caps on both. SurgePV pricing is custom per organization but typically lands in a similar range — without the 10-project monthly limit and without needing AutoCAD ($2,000/year extra) for SLD generation. For a team running 30+ projects per month, the effective cost difference per project favors SurgePV by 50-70% because there are no overage fees or external tool dependencies.
Is SurgePV's simulation accuracy as good as HelioScope?
Yes. SurgePV uses the same module-level simulation methodology that gives HelioScope its DNV GL validation, with similar irradiance database coverage and component libraries. Both tools deliver bankable yield reports for project finance. The functional difference is workflow: SurgePV's accuracy comes packaged with proposal generation, financial modeling, and project management — HelioScope requires you to export to a separate tool for each.
How long does migration from HelioScope to SurgePV take?
For most teams, the migration takes 2-4 weeks of overlap. Week 1: import your component library, set up your branded proposal templates, and migrate 2-3 active projects to verify the workflow. Week 2: train the design team on SurgePV's interface (most HelioScope users are productive within 1-2 days due to similar paradigms). Weeks 3-4: complete the cutover and cancel HelioScope. There's no project file format converter — designs are rebuilt in SurgePV — but the rebuild is fast because the underlying inputs (site, modules, inverters, layout intent) transfer directly.
Does SurgePV support battery (BESS) modeling, which HelioScope doesn't?
Yes. SurgePV models battery storage natively for both AC-coupled and DC-coupled configurations, including time-of-use optimization, peak shaving, and self-consumption modes. HelioScope's lack of native BESS modeling forces users to pair it with Energy Toolbase or Homer Energy at $1,200-3,000/year additional cost. For commercial projects where storage is increasingly required, SurgePV eliminates that second-tool dependency.
Can SurgePV handle utility-scale projects above 15 MW?
Yes. SurgePV has no upper system size limit. Teams use it for designs ranging from residential 5 kW rooftops to 100+ MW utility-scale ground-mount projects. HelioScope's 15 MW hard cap requires a separate utility-scale tool (typically PVsyst or PVCase) for larger projects, which means duplicate component libraries, two simulation engines to validate, and inconsistent yield methodologies between development stages.
Will my HelioScope projects transfer to SurgePV?
Project files don't transfer directly between platforms — there's no industry-standard interchange format for solar designs. However, the underlying inputs do transfer: site address, module and inverter selections, target system size, layout strategy, and financial assumptions can all be re-entered in SurgePV in 15-30 minutes per project. Most teams use the migration as an opportunity to rebuild active proposals with SurgePV's improved presentation rather than recreating completed designs.

About the Contributors

Author
Keyur Rakholiya
Keyur Rakholiya

CEO & Co-Founder · SurgePV

Keyur Rakholiya is CEO & Co-Founder of SurgePV and Founder of Heaven Green Energy Limited, where he has delivered over 1 GW of solar projects across commercial, utility, and rooftop sectors in India. With 10+ years in the solar industry, he has managed 800+ project deliveries, evaluated 20+ solar design platforms firsthand, and led engineering teams of 50+ people.

Editor
Rainer Neumann
Rainer Neumann

Content Head · SurgePV

Rainer Neumann is Content Head at SurgePV and a solar PV engineer with 10+ years of experience designing commercial and utility-scale systems across Europe and MENA. He has delivered 500+ installations, tested 15+ solar design software platforms firsthand, and specialises in shading analysis, string sizing, and international electrical code compliance.