How does the GridProjeX and SolarProjeX integration work?

A coordinator searches for a specific job in either system and links it to the matching record in the other, one job at a time. GridProjeX then pushes its current permit, interconnection, and PTO status onto the linked SolarProjeX job, into a field dedicated to that status rather than SolarProjeX's own job status field.

Does the integration import jobs automatically?

No. Every link is a deliberate, one-job-at-a-time action a person takes after searching. There is no bulk import path.

SolarProjeX integration

Your CRM and your interconnection record, linked one job at a time.

A coordinator in either system searches for the matching job and links it. From that point on, GridProjeX's permit, interconnection, and PTO status shows directly on the job inside SolarProjeX.

CRM integration

One job, searched and linked, never a bulk import.

GridProjeX and SolarProjeX, also from CivyxIQ, connect through a search-and-link flow in both directions. A coordinator picks exactly one match; nothing pulls automatically in bulk.

From GridProjeXSearch SolarProjeX by customer name, address, or work order number, see the matching jobs, and link the right one. GridProjeX creates or updates the one matching project, matched by SolarProjeX’s own job id so linking the same job twice never creates a duplicate.

From SolarProjeXThe same flow in reverse: search GridProjeX’s projects from inside a SolarProjeX job and link the match. GridProjeX’s permit, interconnection, and PTO status appears on that job immediately.

Status flows one way, into the CRMOnce linked, GridProjeX pushes its current status onto the SolarProjeX job. That status lands in a field dedicated to it — it never touches SolarProjeX’s own job status, which drives that company’s field operations.

No shared database, everThe two systems talk through an authenticated API, each keeping its own database and storage. A change on one side cannot corrupt the other by construction.

Why one at a timeAn early version of this connector pulled every historical job on a first sync. It was rebuilt to require a person to search for and link one specific job, every time — the only import path that exists now.

See the full installer feature set, or how PTO status is built from the same project record that gets pushed to SolarProjeX.