Migrate from GBuilder to Pipedrive

GBuilder contacts migrate as Pipedrive People. The Name field splits into first_name and last_name for Pipedrive's separate fields. Email, phone, and job title map directly. GBuilder contact custom fields become Pipedrive Person custom fields. The primary_company link maps to org_id, requiring the Company migration to complete first.

GBuilder companies map to Pipedrive Organizations. Company name, domain, industry, and employee count migrate as Organization fields. Address data maps to Pipedrive's address compound field. Parent-company hierarchies in GBuilder become Parent Organization links in Pipedrive. The parent_org relationship requires validation to prevent circular references.

GBuilder projects do not map 1:1 to Pipedrive Deals because Pipedrive Deals lack the multi-phase structure of GBuilder projects. FlitStack AI creates one Pipedrive Deal per GBuilder project, using the project name as Deal name and the most recent project phase as the initial Stage. Project budget and dates map to Deal value and expected close date.

GBuilder project phases (e.g., Pre-Construction, Design, Procurement, Construction, Closeout) map to Pipedrive Stages within the target Pipeline. Each phase name becomes a Stage name. Probability weights are assigned based on phase position in GBuilder's lifecycle. Stage transition dates are preserved as custom datetime fields in Pipedrive.

GBuilder stakeholders linked to a project become associated with the corresponding Pipedrive Deal. The association role (e.g., Architect, Contractor, Owner) migrates as a custom field on the Deal-Person link or as a Deal custom field listing stakeholder roles. Pipedrive supports multiple People per Deal.

GBuilder site visits, meetings, and coordination events migrate as Pipedrive Activities. Meeting type maps to Pipedrive's activity type (Meeting, Call, Task). Original timestamps, duration, and assigned user preserve. Activity notes map to Pipedrive Activity notes. Parent deal or person links maintain traceability.

GBuilder attachments on project records migrate as Pipedrive Files attached to the corresponding Deal. FlitStack AI re-uploads files to Pipedrive's storage using the Pipedrive API. Files exceeding Pipedrive's 25MB limit are flagged for chunked upload or alternative delivery. Attachment metadata including original upload date preserves as custom fields.

GBuilder project managers and team members resolve by email match against Pipedrive Users. Unmatched users are flagged before migration with a manifest listing each unmatched owner and record count. FlitStack AI assigns unmatched GBuilder owners to a fallback Pipedrive user or leaves OwnerId blank pending admin invitation.

GBuilder custom fields on Contacts, Companies, Projects, or Activities create Pipedrive custom fields on the corresponding entity (Person, Organization, Deal, or Activity). Pipedrive requires pre-creation of custom fields before data import; FlitStack AI generates a Pipedrive setup script as part of the migration plan.

GBuilder workflows and automation rules (e.g., phase-change triggers, notification rules) do not migrate. FlitStack AI exports workflow definitions as JSON for your Pipedrive admin to reference when rebuilding in Pipedrive Automations. Sequence and email template rebuilding is not included in the data migration scope.