Find how much you have
Sign in to the Aurora app as an Admin. Team Members can also see every project under the standard roles, but a Limited Team Member only sees their own, and on Build, Grow and Scale plans the Teams and Advanced Roles features can narrow who sees which projects. An Admin login avoids a short count.
Open Projects. Aurora lands you there after login. Each project is one site address, and a project can hold several designs.
Look for a project total on that page. Aurora's help center doesn't describe one, so if your screen doesn't show it, use the API step below or ask Aurora support for a count of projects and designs on your account.
Open a handful of projects. The project dashboard lists every design for that address, and the Milestone column shows any milestone your team assigned to each one (such as Offer, Sold, Installed or Canceled). Average the designs per project to estimate your design count, and mark it Estimated.
For an exact count, have an Admin create an API key under Settings > API tokens, then page through the List Projects call (up to 250 per page) and add up the results. List Designs returns the designs inside one project. This needs API access on your plan.
Note the created date on the last project of the last page. List Projects returns newest first, so that is the oldest project and your records start.
What to put on your intake
Your intake has five boxes for each system. Here is what goes in each one for Aurora Solar.
- What does it hold?
- Solar projects, one per site address, with designs, system sizes, pricing, financing choices, proposals, milestones and signed agreements.
- Data types
- Structured records and Text. Add Image only if your team attaches photos to project notes.
- How big is it?
- Designs if you can count them, since that is the intake default for Aurora. If you can only count projects, report Projects and say so in the notes.
- Verified or estimated
- Verified if the number came from paging the API or from a count Aurora gave you. Estimated if you averaged designs per project or counted a sample.
- Records start
- The created date of your oldest project.
Exporting the full history
If a buyer licenses your records, this is how the full history comes out of Aurora Solar.
Nothing is pulled until a buyer licenses the data and the scope is agreed: which projects, which date range, and which fields (for example project and design records, milestones, pricing and financing).
Confirm API access. Aurora lists its Sync API in the Build, Grow and Scale plans, and its help center says API access is not on every account, with self-serve credit accounts left out. A 403 from an endpoint means it is not provisioned for your key, and Aurora's account team has to switch it on.
An Admin creates a restricted key under Settings > API tokens, in the Restricted Keys section, with + New Key. Switch on only the endpoints in scope. Aurora's docs suggest a separate restricted key for each outside party.
Run the pull: List Projects page by page, then each project's designs, design summary, pricing, financing and agreements as the scope allows. The default limit is 90 requests a minute and some endpoints set their own, so pace the job.
For a single design, Design mode > Download > Production Data gives a CSV of 8,760 hourly production values. That is a manual route, only practical for a few designs.
When the pull is done, an Admin deletes the restricted key from the API tokens page. Files are de-identified before they go to a buyer.
We only ask for an export after you sign a license and agree the scope. Sizing your data for the intake never needs one.
Limits to know
- We found no one-click export of every project in Aurora's help center. The routes it documents are the API and per-design downloads, so ask Aurora support if neither fits your account.
- API access depends on your plan. The Sync API appears in the Build, Grow and Scale plans, and the Design API is an extra that Aurora says is signed up for at the point of sale. Check with Aurora what your account includes.
- The List Projects response has no total count field, so you count by paging through the results. The default page is 100 projects, and the maximum is 250.
- The API's default rate limit is 90 requests per minute, and some endpoints have their own limits. If you go over, Aurora points you to the response body and the Retry-After header to see when you can call again.
- Executed agreements sent through the older Contract Manager, which used Dropbox Sign, stop being viewable or downloadable in Aurora on March 31, 2027. Download them before then if you want to keep copies. You can filter the Project Index by Updates > Agreement Signed to find the projects that have one.
- A project can have only one Sold design at a time. Marking a new design as Sold turns the earlier one into Canceled, so a Canceled milestone can mean a design was replaced, not that the customer walked away.
This guide isn't legal advice. Check your contracts, and any recording-consent rules that apply, with your own lawyer.
Why buyers value it
Aurora ties a site, its energy use and a set of designs to what happened next. Each design carries a system size, pricing and a financing choice, and the milestones your team assigns record how it played out: Offer, Sold, Change order, Revised, Installed, Permission to operate or Canceled. That pairing of what was proposed with what the customer did is hard to find anywhere else.
It also shows how designs get revised before and after a sale. Years of that history across different sites, utilities and financing structures are useful for models that estimate production, pricing and how often offers turn into live systems.
What stays private
Anything that identifies a homeowner comes out before a buyer sees it. In Aurora that means the customer's contact details, the site address and map coordinates, and energy bill or consumption data tied to the address. Project notes and attachments are free text that can name people, so they are checked for names and contact details before delivery.
Signed agreements, financing applications and credit-related data are excluded by default, along with user logins, license details and API keys. Satellite imagery and the weather and elevation datasets Aurora pulls in for shading and production come from other providers, so we treat them as third-party. What you license is your own design and outcome records, not their source data.
Common questions
Sources
Vendor documentation, checked . Screens and plans change, so if a step looks different in your account, check with Aurora Solar.
- Aurora Help Center: Creating a New Project (opens in a new tab)
- Aurora Help Center: Admin Quick Start Guide (opens in a new tab)
- Aurora Help Center: User Management: Roles (opens in a new tab)
- Aurora Help Center: How to manage Users and Licenses (opens in a new tab)
- Aurora Help Center: Milestones in Aurora (opens in a new tab)
- Aurora Help Center: API Tokens (opens in a new tab)
- Aurora Help Center: Access Scopes (opens in a new tab)
- Aurora Help Center: Enterprise Plans: Build, Grow, and Scale (opens in a new tab)
- Aurora Help Center: Downloading your Dropbox Sign agreements (opens in a new tab)
- Aurora Help Center: Hourly Production Data Export (opens in a new tab)
- Aurora Help Center: Add Notes and Attachments in Sales Mode (opens in a new tab)
- Aurora Help Center: Data Sources used in Aurora for Shading Analysis (opens in a new tab)
- Aurora API: Overview (opens in a new tab)
- Aurora API reference: List Projects (opens in a new tab)
- Aurora API reference: List Designs (opens in a new tab)
- Aurora API reference: Authentication (opens in a new tab)
- Aurora API reference: Rate Limits (opens in a new tab)