Answer
To migrate from Aurora Solar to SurgePV, archive the source records, demonstrate a representative project and approve the new workflow before canceling access. Aurora documents DXF and hourly-production exports, but direct project transfer is unverified. The deciding factor is accepted output and record continuity, not a promised number of migration days.
Last updated: November 2026
Switching design platforms puts active customer work, historical records and familiar workflows in the same transition. A useful migration plan separates what can be exported, what must be reconstructed and what still needs a demonstration before the team commits.
This guide keeps the seven-step migration sequence and export checklist, but uses acceptance criteria rather than a guaranteed completion date. Run a representative pilot, inspect the records it produces and agree the commercial scope before retiring the existing platform.
SurgePV publishes this post and sells solar design software.
Check migration fit with a real Aurora project
Bring an export and a proposal example to a SurgePV demo to identify the work needed for a pilot.
Book a DemoChecking cost first? See the SurgePV pricing page.
Why Teams Migrate from Aurora Solar in 2026
Evaluate a switch against the work your team needs to deliver. Cost, supported project types, output requirements and customer handoffs are legitimate reasons to compare platforms, but they are questions to investigate rather than proof that one product is always better.
Compare published prices and documented features for the actual region and plan. Aurora’s pricing page publishes a Basic annual price of $1,620 per user, accessed November 2026. Its SLD template documentation also describes single-line diagrams for tenants in Europe. Check the region, plan and scope relevant to your account.
Assess these areas using a representative job:
- Project fit: Can the proposed workflow represent your roof or site geometry and required equipment? Retain a sample output rather than relying on a feature label.
- Market fit: Are the location data, units, tariffs and required documents suitable for the markets you serve? Local approval remains separate from software capability.
- Engineering handoff: Can the responsible reviewer reconstruct the design basis from the output? Identify any tools or professional services that must remain in the workflow.
- Commercial fit: Compare written quotes with the same seat count, billing period and required services. Include overlap and migration labor.
Use the Aurora and SurgePV comparison to frame questions, then validate the requirements in your own pilot. A switch is justified by accepted outputs and a credible operating plan, not an arbitrary count of feature wins.
Pro Tip
Ask each role to name its critical tasks and a sample deliverable. Turn those into pass criteria before the demo so an attractive feature does not distract from a missing workflow.
Pre-Migration Checklist: What to Export Before You Cancel
Inventory your projects and data before changing access. The Aurora documentation opened for this guide supports DXF design exports and hourly production CSV downloads. It does not verify a direct transfer into SurgePV, bulk-migration availability or your account’s access entitlements.
What to Pull Out of Aurora
| Record | Verified Export or Retention Approach | Migration Treatment |
|---|---|---|
| Design geometry | Aurora documents DXF export | Preserve as reference; verify receiving workflow |
| Module and string layout | Included among documented DXF layer options | Reconcile against the approved layout |
| Hourly production | Aurora documents CSV with 8,760 hourly values | Retain as a comparison record |
| Customer consumption | Retain original utility files and bills | Check format and permissions separately |
| Equipment schedule | Retain exact model documents and project selections | Review supported equipment before rebuilding |
| Proposal and agreement | Preserve the issued document and signature record | Maintain the customer-approved version |
| Customer and pipeline records | Retain the controlling CRM record | Define identifiers and field ownership |
| Electrical drawings | Preserve issued files and revision history | Route recreated outputs through review |
The export entries follow the Aurora pages linked in the export section below. Other rows are a recommended archive checklist, not claims that a specific export button or integration exists.
An exchange format can preserve geometry without preserving all design logic, model settings or approval status. Do not call a DXF import a complete migration until the receiving workflow has been demonstrated. Keep the original record available for comparison and document what must be entered again.
Critical Files to Save Before Cancellation
Create a project manifest listing every expected file, its revision and owner. Include the released layout, energy outputs, underlying assumptions, customer proposal, agreement, equipment documents and any engineering approvals. For a project that remains active, record which platform is the system of record.
Store the archive in an access-controlled location using stable project IDs. Customer names alone can be ambiguous. Open a sample of files from the archive without relying on an active Aurora session, and check that attachments and linked evidence are actually retained.
Keep retention and privacy requirements under your organization’s policy. A closed-lost project does not automatically justify deletion, and a closed-won project may still need support records. Agree what must remain accessible for customer questions, warranty work and contractual obligations.
The 7 Step Aurora to SurgePV Migration Process
The migration follows a sequence because later work depends on accepted source records and equipment choices. Independent preparation can run alongside it, but do not scale project rebuilding before the pilot has passed.
Step 1: Audit Active Aurora Projects
Build a project list and assign a disposition: finish in the existing workflow, rebuild through a reviewed change, or retain as an archive. Record customer commitments, outstanding approvals, owner and next milestone for each project.
- Active proposal: Preserve the issued offer. Change it only through an agreed revision process.
- In design: Consider it for the pilot if no downstream party relies on the current output.
- Closed won: Retain the full handover and approval history, including later support needs.
- Closed lost or stale: Apply your retention policy and sales process rather than a universal age cutoff.
Choose pilot jobs that represent the team’s real difficulties. Include a straightforward roof and a project with the geometry, shading or financial conditions that matter to your business. Do not select only the easiest examples and infer that every live job will transfer equally well.
Step 2: Set Up the SurgePV Workspace
Start with a guided demonstration and written scope for access, onboarding and implementation. A demo request does not start a subscription. Agree which users need access and which account settings are available before planning a large rollout.
Prepare your organization name, brand assets, preferred units, currencies and proposal requirements. Ask how user permissions and project ownership work in the offered configuration. Do not assume role names or controls from another platform exist unchanged.
Assign an internal administrator and a design reviewer. Keep decisions about pricing assumptions and approved equipment with named owners. Record who can alter shared settings, who approves customer outputs and how the team will recover from an incorrect change.
Use a setup checklist signed off by the people who will use the workflow. If a required permission or setting is unavailable, decide whether a documented process can cover it or whether it blocks adoption. Resolve that before moving active projects.
Step 3: Export Aurora Data Project by Project
Follow Aurora’s current help pages for supported exports, then inspect the files. The export section below summarizes the documented DXF and hourly-production workflows. Account permissions, region and product changes may affect what you see, so resolve missing options with Aurora support.
Record project ID, design revision, export date and the person making the export. Keep the source file untouched and perform any transformation on a separate copy. A clean audit trail helps explain differences later without guessing which version was used.
Where you used Aurora SLD templates, retain the resulting drawings and relevant template information. Aurora’s documentation says template edits apply to future uses rather than retroactively updating existing SLDs. Review each project’s issued drawing instead of assuming the latest template describes it.
Do not assume SurgePV regenerates an equivalent approved diagram automatically. Demonstrate the required electrical output and have the responsible reviewer assess it against the original project basis.
Step 4: Build Your SurgePV Component Library
Prepare the equipment list before rebuilding pilot designs. The goal is consistent identification, not a large catalogue assembled without review.
Collect exact module and inverter model identifiers, current manufacturer documents and any approved alternatives. Include other equipment relevant to the project, but ask which items the proposed workflow represents and which remain in external schedules.
Record the source document, revision and reviewer for every entry used in the pilot. Similar model names can conceal different electrical ratings or regional versions. Do not infer warranty terms or certifications from a neighboring product.
Have one owner resolve duplicates and changes. If a required model is missing or its data differ from the approved project, hold that design until the discrepancy is settled. Library preparation time depends on the scope and evidence quality; no universal setup-hours estimate is assumed here.
Step 5: Rebuild Your Proposal Template
Open your most recent Aurora proposal PDF and identify the elements that matter:
- Cover page (logo, project address, system size, customer name)
- Executive summary (energy offset, savings, payback)
- System specifications (modules, inverters, layout drawing)
- Production estimate (year 1, year 25, lifetime)
- Financial analysis (cash purchase, loan, lease, PPA)
- Warranty and installation timeline
- Company credentials and case studies
Use the pilot to demonstrate how those sections can be represented in the offered proposal workflow. SurgePV documents proposal generation, but template conversion, editing controls and implementation effort need agreement. Keep contractual and warranty wording under the appropriate review.
For multiple proposal types, prepare separate sample outputs and a controlled list of differences. Verify supported template organization during onboarding. Check that changing one version does not silently alter wording relied on by another customer group.
Step 6: Run a Parallel Simulation to Validate Outputs
Rebuild representative projects and compare the input basis before comparing annual totals. The reviewer should know which differences are intentional and which remain unexplained. There is no universal percentage tolerance that makes two platforms equivalent.
| Validation Item | Acceptance Basis |
|---|---|
| Equipment and DC capacity | Exact project identity and accepted configuration |
| Weather and location | Documented source, period and coordinate basis |
| Shading | Comparable geometry, method and reported metric |
| Annual AC energy | Explained difference under reviewed assumptions |
| Consumption | Same source, time basis and meter boundary |
| Financial outputs | Same tariff, costs, financing and eligible incentives |
| Proposal | Accepted values, wording and version history |
Do not tune losses merely to force the new total to match the old one. Different weather datasets or model methods can legitimately produce different outputs. Explain the difference, assess whether it affects the intended decision and retain the reviewer’s acceptance record.
Use generation and financial modeling in the pilot to inspect the scenarios relevant to your customer. Verify required report detail and export formats with a real sample. Where another tool remains necessary, include it in the future workflow and cost comparison.
After technical review, ask a user who did not build the pilot to reproduce the task from the handover notes. That reveals whether the process is repeatable or depends on one person’s memory.
Step 7: Cancel Aurora and Reclaim Budget
Set the retirement date only after the pilot, archive and active-project decisions are accepted. Review Aurora’s actual contract and obtain written instructions for cancellation, notice, renewal, final billing and post-termination data access. Do not assume a particular proration or refund policy.
Before reducing access:
- Verify the archive and file manifest, including customer-issued records.
- Assign ownership for every remaining active project and customer question.
- Demonstrate any required integrations and exception handling.
- Record which licenses remain necessary for engineering or other deliverables.
- Have the administrator schedule access changes after the final export and checks.
Keep a rollback decision available during the pilot. If a required workflow fails, stop expanding migration rather than forcing live projects into an unaccepted process. A temporary overlap has a cost, but an unsupported cutover can create a larger operational problem.
How to Export Project Data from Aurora Solar
Aurora’s help centre provides export instructions for particular records. These instructions describe export from Aurora, not import support in SurgePV. Verify both ends of the workflow independently.
Exporting DXF Site Plans
The Aurora DXF export guide describes opening Design Mode, choosing Export, selecting DXF and choosing layers. Listed layers include roof outlines and obstructions, module layout and string configuration, setbacks and boundaries, and applicable conduit paths.
DXF means Drawing Exchange Format. Check the units when opening the file in a compatible application; a geometry file with the wrong scale is not a usable migration reference. Preserve a complete reference export and agree any smaller layer selection with the receiving reviewer.
Verify boundaries and dimensions against the original drawing before rebuilding. Keep unidentified layers visible until someone understands them. A hidden obstruction or boundary can make a clean-looking plan incomplete.
Exporting Hourly Production Data
Aurora’s hourly-production export instructions describe Download, then Production Data in Design Mode, producing a CSV with 8,760 hourly production values. The page was updated in October 2026 and accessed for this guide in November 2026.
Inspect the actual column headers, units and time convention. Do not assume the file includes temperature, irradiance or every intermediate model result. Save the simulation settings separately so the reviewer can interpret the output.
Retaining Consumption Interval Data
Keep the original utility files, bills and consent records used in the project. Ask each vendor to demonstrate any required interval-data export or import with a representative file. Record supported formats, missing fields and any manual entry before planning the transfer.
Ask both vendors to demonstrate the required handling of your sample file. Check timestamps, time zone, gaps, duplicate intervals, units and meter boundary. If direct transfer is unavailable, agree an acceptable reviewed workflow before moving affected customers.
Retaining Proposal PDFs
Preserve the exact customer-issued proposal and any signed agreement through the available account workflow. Verify that the downloaded record opens independently and includes the pages and attachments the customer received.
A PDF is a record of the proposal, not necessarily an editable template or a transfer of signature history. Retain original approved copy and brand assets where available. Keep audit records from the signing platform separately when required by your process.
State-by-State and Country-by-Country Migration Notes
Market requirements should be acceptance criteria in the pilot. A software switch does not transfer local approvals or prove that a new output meets an authority’s requirements.
United States
List the adopted code basis, authority requirements and electrical deliverables needed for your projects. Ask the responsible reviewer which outputs can come from the new workflow and which still need separate drafting or engineering. Do not retire a CAD seat solely because another product lists electrical support.
Canada
Use a Canadian sample project with the relevant utility, equipment and review requirements. Verify the needed units, tariff representation and report scope. Do not assume provincial structural presets or local compliance automation without demonstrated product documentation.
European Union
Treat each country and project type separately. Aurora’s SLD documentation is explicitly limited to tenants in Europe; this is a reason to check account-specific functionality, not to assume either platform has identical regional scope. Keep the local engineer’s acceptance criteria in the migration plan.
India and Southeast Asia
Use actual project geometry, equipment documents and customer billing evidence from the market being served. Verify imagery suitability, financial assumptions and required submission documents. Do not substitute a broad country-coverage claim for a reviewable sample.
Australia and New Zealand
Check the actual equipment approvals, network requirements and locally adopted installation rules with qualified professionals. Demonstrate the requested workflow before relying on a library label. Keep network approval and software validation as separate milestones.
Across all markets, preserve the source of local assumptions and assign an owner for updating them. The migration should not silently reset tariff, currency, loss or electrical settings to defaults from another region.
Cost Comparison: Aurora + AutoCAD vs SurgePV
Compare the cost of the complete accepted workflow. Published subscription prices are a starting point; they do not prove equal feature scope or establish migration savings.
Published SurgePV Annual Plans
The following USD rates come from SurgePV’s published pricing and approved product record, checked November 2026. Team rates require the stated seats; taxes, implementation scope and contract terms belong in the written quote.
| Plan | Seats | USD per User per Year | Total Annual USD |
|---|---|---|---|
| Individual | 1 | $1,899 | $1,899 |
| Three-seat team | 3 | $1,499 | $4,497 |
| Five-seat team | 5 | $1,299 | $6,495 |
- Individual$1,899
- Three-seat plan$1,499
- Five-seat plan$1,299
Source: SurgePV published pricing; team seat commitments apply, checked November 2026.
Aurora’s Basic annual price cited above is $1,620 per user. It would be misleading to claim SurgePV’s individual plan is cheaper on those figures alone. Compare the actual plans and services your team requires, including retained tools, transition work and contract commitments.
Key Takeaway
The five-seat SurgePV annual total is $6,495 at the published team rate. Savings require your actual Aurora quote, retained tools, migration labor and overlap costs; this table is not a like-for-like feature comparison.
Build a migration scope your team can cost
Use a guided walkthrough to identify required outputs, onboarding work and tools that must remain.
Book a DemoChecking cost first? See the SurgePV pricing page.
Small Installer Cost Review
For a small team, list the tasks that require paid access and the work that can remain in an archive. Obtain a quote for the actual number of users instead of extrapolating a team discount to an unsupported seat count. Include the owner’s time spent reviewing the pilot and training.
Mid-Size EPC Cost Review
For a team with several designers, measure project rebuilding and shared-template work separately. Identify whether the bottleneck is review capacity, customer approvals or a data integration. A lower per-user price does not resolve a delayed engineering handoff.
Larger Team Cost Review
For larger deployments, obtain a written commercial and implementation proposal. Include access administration, support, regional templates, integration maintenance and ongoing quality review. Keep a named owner for each cost rather than treating all implementation work as included.
Calculate first-year transition cost separately from steady-state annual cost. The first includes overlapping subscriptions, archive preparation and training; the second includes the services required after cutover. Count a retired license as a saving only when the responsible team has accepted its replacement.
Common Migration Pitfalls and How to Avoid Them
Use the following review points to catch gaps before they affect active projects. They are practical failure modes, not a quantified survey of migrations.
Pitfall 1: Skipping Parallel Validation
Compare representative projects and retain the accepted assumptions. Differences in weather, geometry or loss treatment can affect results. Resolve unexplained differences before a new proposal is issued; matching totals alone is not enough.
Pitfall 2: Moving Customer Proposals Without Revision Control
Preserve the issued offer and identify what has changed if a new version is necessary. The customer’s equipment, price, warranty or savings assumptions should not change silently because a new template uses different defaults.
Pitfall 3: Adding Equipment Without a Shared Review
Use exact model identifiers and a controlled source document. Assign an owner for duplicates, corrections and approved substitutions. Warranty wording should come from the applicable manufacturer terms, not a designer’s memory.
Pitfall 4: Treating Training as Attendance
Have users complete a realistic task and explain the resulting output. Designers need to understand the model basis; sales staff need to identify approved figures and open conditions. Repeat the relevant exercise when a shared template changes.
Pitfall 5: Canceling Before the Archive Works
Open retained records outside the original account and check their completeness. Review cancellation and data-access terms in writing. The cutover date should follow acceptance of those checks, not a calendar target that assumes every export succeeded.
Team Onboarding Timeline
Schedule by accepted milestones rather than promising a migration duration from team size. Project complexity, archive quality, integration requirements and reviewer availability can all change the work.
| Stage | Work | Exit Evidence |
|---|---|---|
| Inventory | Project dispositions and source files | Accepted project register |
| Pilot preparation | Equipment, settings and sample proposals | Ready-to-run pilot inputs |
| Validation | Rebuilt outputs and explained differences | Reviewer acceptance |
| Controlled rollout | User tasks and live-work boundaries | Documented operating procedure |
| Retirement | Archive, contract and access checks | Authorized cutover record |
Illustrative Four-Week Planning Framework
The following is a planning template, not a delivery promise. Extend any stage if its exit evidence is missing.
Week 1: Inventory projects, agree pilot scope and gather source documents. Name the migration owner and reviewers. Resolve commercial access and onboarding questions before booking the team for training.
Week 2: Run the pilot and document output differences. Review sample proposals, equipment selections and financial assumptions. Capture missing workflow requirements as decisions rather than informal workarounds.
Week 3: Train users on accepted workflows and introduce new work only where the pilot has passed. Keep a visible exception list and a route back to the prior workflow if a release-controlling problem appears.
Week 4: Review archive completeness and remaining active projects. Decide whether the cutover criteria are met; if they are not, retain the required access and update the plan. Do not cancel a subscription simply to make the example timetable appear successful.
SurgePV Features That Replace Aurora Pain Points
Use SurgePV’s documented product scope to define the pilot. It includes 3D roof modeling, array layout, shading analysis, energy-yield and financial modeling, electrical workflow support, bill-of-materials output and proposal generation. Results still depend on inputs, configuration and review.
Electrical Workflow Support
Ask for the exact electrical deliverables your team needs and inspect a sample with the responsible reviewer. Do not describe output as automatically compliant, stamped-ready or a replacement for engineering approval. Keep any unsupported deliverable in the retained workflow.
Layout and Shading
Demonstrate a representative site rather than assuming support for every carport, tracker or racking configuration. Record the geometry, obstruction assumptions and report details that the reviewer can inspect. The scope of the accepted pilot should define the initial rollout.
Energy Modeling
Review source data, equipment models, loss assumptions and result interpretation. If a lender needs a particular uncertainty method or report, have the lender’s reviewer assess that requirement separately. The approved scope does not justify a blanket bankability claim.
Bill of Materials
Compare BOM output with the released design and the buyer’s required fields. Check quantities, units, model identity and revision handling. Any file transfer or automatic purchasing workflow needs its own demonstration and acceptance.
Financial Modeling
Review the customer-specific assumptions behind the model, including cost, usage and tariff treatment. Keep tax and incentive eligibility with the appropriate adviser. The model should expose uncertainty rather than imply a guaranteed savings result.
Proposal Generation
Use SurgePV’s design workflow to create a sample project and inspect the resulting customer output. Confirm required branding, editing, review and export behavior during the demonstration. Do not assume AI assistance, signature-provider integrations or template conversion are included without supporting scope.
What to Tell Your Customers During Migration
Communication during a tool switch matters more than people think. Customers who see the same logo on a different-looking proposal sometimes pause to ask whether they are dealing with the same company.
Three short rules:
- Active proposals stay in the original tool. Do not switch a customer mid-flight. Wait until the current proposal closes or expires.
- New customers get the SurgePV branded proposal from day one. Train the sales team to skip any reference to a “new tool” , to the customer, the SurgePV proposal is just your proposal.
- Send the same email cadence as before. The proposal follow-up sequence, payment confirmation emails, and post-install reports should look identical to what your customer received pre-migration.
If electronic signatures are required, verify the provider, integration and audit-record handling before rollout. Keep the existing signing process where needed until the replacement is accepted. Do not promise customers that their access or signing experience will be unchanged without checking it.
Migration Support: What SurgePV’s Onboarding Team Handles
Agree onboarding work in writing before assigning a deadline. The pricing page mentions onboarding, but that does not specify a migration manager, template-recreation service, training hours or a particular support channel for every account.
Ask the team to document:
- Which setup and training activities are included, and who performs them.
- Whether sample exports can be assessed before commitment.
- Which records can be transferred and which require reconstruction.
- Who reviews technical differences between model outputs.
- Whether proposal conversion or integration work has a separate scope.
- What support route and response expectations apply during rollout.
Keep vendor tasks separate from internal responsibilities. Your team still owns customer commitments, source-data quality, retained records and professional approval. A useful onboarding plan names deliverables and acceptance conditions rather than relying on a general promise of migration help.
Track effort during the pilot to estimate the remaining work. Count preparation, rebuilding, review and correction separately. Use those observations to decide whether the team can absorb the transition alongside live projects or needs a staged rollout.
Conclusion
A controlled migration starts with retained records and ends with accepted workflows. The seven steps provide a sequence, but the pilot and archive checks determine when the team is ready to cut over.
Action items to start this week:
- Classify active projects and name the system of record for each.
- Gather representative exports, approved equipment documents and an issued proposal.
- Assign the migration owner, technical reviewer and archive reviewer.
- Agree the written scope and acceptance criteria before scheduling cancellation.
Bring those records to a SurgePV migration-fit demo. Use the session to identify what can be demonstrated now, what needs further validation and what remains in the existing workflow.
Frequently Asked Questions
Can you import Aurora Solar projects directly into SurgePV?
Direct project import is not verified by the product scope used for this guide. Aurora documents DXF and hourly-production exports, but exporting a file does not prove the receiving platform can recreate the project. Demonstrate your sample workflow before planning a bulk migration.
How long does an Aurora to SurgePV migration take?
The duration depends on project volume, reconstruction work, integrations and reviewer availability. Use a pilot to measure the effort and set milestone-based acceptance criteria. The four-week plan in this guide is illustrative, not a delivery guarantee.
What can I export from Aurora Solar before canceling?
Aurora documents DXF design exports and a CSV containing 8,760 hourly production values. Retain customer-issued documents, original consumption files and approval records as well. Check account-specific options and verify the archive before changing access.
Does SurgePV cost less than Aurora Solar?
The answer depends on the actual plans, seats and services required. Aurora publishes a Basic annual rate of $1,620 per user, while SurgePV publishes $1,899 for an individual and lower per-user rates at stated team commitments. Compare complete written quotes and transition costs.
What happens to active customer proposals during migration?
Keep the issued proposal and its source records under revision control. Finish it in the existing workflow or make a deliberate, reviewed change. Do not silently replace customer-approved figures with defaults from a new template.
Can I run Aurora and SurgePV in parallel?
A parallel pilot is possible when you maintain the required access to both products. Define which system controls each active project and who reviews differences. Set retirement criteria rather than assuming a fixed overlap period.
Will my CRM integrations work after switching?
Existing integrations should be treated as unverified until the new workflow is demonstrated. Check identifiers, field mapping, permissions, failed transfers and duplicate handling. Obtain written scope for any required connector or implementation work.
Where this fits
This article is part of SurgePV's Solar Design hub, which works through the topic from first principles to the decisions a project team actually has to make.


