Administration - Import Legacy (Completed) Project Data
Where found? Administration menu > Lead and Project Data > Import Completed Projects (at the bottom)
Accessibility? Users with administration permissions only.
How used?
Do you have existing customer data in another CRM system? Or spreadsheet? If you can get that data into a spreadsheet, you can import it into SolarNexus so that all of your customers are in a single place. This allows your company to use the Universal search bar in SolarNexus to quickly retrieve existing customer and project information. DO NOT USE THIS IMPORT FOR NEW LEADS (Learn more about batch importing new leads). This feature is for projects that are already complete.
You must provide a completion date in the import. You can also import information about the PV system and other custom data fields - enabling a rich set of data.
The Import screen provides a sample CSV that shows a couple sample records. It also provides a field requirements guide.
TIP: Before trying to import a large file, SolarNexus strongly suggests trying out the import with a small number of records initially in case of data formatting issues which we have found to be extensive when pulling data from other CRMs.
SolarNexus finds that many CRMs are pretty lax when it comes to data quality. Cleaning up and manipulating poorly formatted and incomplete data can be a fairly significant chore which can requires a fair amount of expertise in using Excel functions. SolarNexus offers a service to convert your data to an acceptable import file. Cost of the service depends on the quality and quantity of the data you have. Submit a Request with a copy of your data file so that SolarNexus can review and provide a proposal for importing the data.
How SolarNexus Handles Duplicate Project Records
If SolarNexus finds two records with the same site address, it checks to see if the project name is unique. Its possible to have more than one project at a site address (for example, adding a second system at a later date). If you are importing records that may have a duplicate site address, make sure that you include a unique project name for the other record. If SolarNexus detects a that a record being imported is a duplicate of an existing project, it skips importing that record, and provides a list of duplicates found in the file you are trying to import. If a duplicate customer record is already found in SolarNexus (if the contact name/email already exists), SolarNexus adds a new project for that already existing customer/contact as long as the project name is unique.