Migrate from Sunbase Data to Pipedrive

Sunbase Leads (captured through door-to-door forms, web capture, or manual entry) map directly to Pipedrive Leads. Lead source, status, and assignment data migrate as standard Lead fields. Some lead fields in Sunbase are tied to automation workflows that may not transfer; we flag any workflow-dependent lead fields during scoping so the customer can assess rebuilding triggers in Pipedrive's automation tools post-migration.

Sunbase Contact records with standard fields (name, email, phone, address) plus industry-specific fields migrate to Pipedrive Person. We extract Contact records from the CRM module export and map each field to the corresponding Pipedrive Person field. Custom contact fields require a field manifest from the customer during scoping; without the manifest, we map standard fields only and flag custom fields for manual mapping in Pipedrive before migration.

Sunbase Client records representing companies or business entities map to Pipedrive Organization. Client records that represent individual contractors or business-owners without a separate Organization record are mapped as Pipedrive Person records instead; we resolve this split using the Client type field during scoping. The client's address and company-level metadata migrate as Organization fields. If Sunbase Clients have a hierarchical relationship (parent company and subsidiaries), this structure is flattened in Pipedrive unless a custom field captures the hierarchy.

Sunbase Deals tracking the full sales cycle (proposals, quotes, pipeline stages) map to Pipedrive Deals. Deal values, stage history, and associated contacts migrate. We map Sunbase deal stages to Pipedrive pipeline stages during the pipeline configuration step. Custom deal fields require explicit mapping during scoping; without a manifest, we map standard deal fields and flag custom fields. Pipedrive Deal ownership is assigned via owner email resolution against the destination User table.

Sunbase Projects representing installation or job-site operations have two migration paths depending on the destination Pipedrive plan. On Pipedrive's Advanced plan ($29/user/mo), Projects are a native object and we map project metadata, status, budget, and linked Work Orders directly. On lower plans, Projects migrate as Pipedrive Deals with a custom project_type field to distinguish them from sales Deals, or as Activity-linked Notes if the customer prefers not to create duplicate Deal records. We confirm the plan-tier decision during scoping.

Sunbase Work Orders containing permit info, task details, and system specifications link to parent Projects and assigned Employees. We extract Work Order records and map them to Pipedrive Activities: permit and specification details migrate as Note records attached to the parent Deal or Project, and actionable tasks migrate as Task records. Work Order status is preserved in a custom field on the Activity so that customers can filter by job status after migration. We resolve the parent-record lookup at migration time using Sunbase's cross-module relationship IDs.

Sunbase Employee records contain HR data, crew assignments, and role metadata. If the destination Pipedrive account uses the same employees as sales users, we provision Pipedrive User records by matching employee email and map role assignments to Pipedrive permission sets. If Sunbase employees are field crews who are also customer contacts in the CRM, we migrate them as Pipedrive Person records instead, with a role assignment captured in a custom field. GPS trail data from Sunbase is exported as a bulk file and mapped to a custom field or attachment on the Person record.

Sunbase Appointments including customer-linked scheduling, dates, times, and assigned contacts migrate to Pipedrive Activities with type set to calendar event. We preserve appointment dates, times, assigned contacts, and status. Sunbase's Google Calendar sync linkage does not transfer; appointments land in Pipedrive's activity timeline without calendar push. The WhoId on the Pipedrive Activity is resolved by matching the Sunbase appointment contact ID against the migrated Person records.

Sunbase Documents including contracts, financing applications, permits, and attachments stored within the platform are extracted as binary files and mapped to Pipedrive Attachments. We preserve file names, upload dates, and associations to the parent record (Contact, Client, Deal, Project, or Work Order). File associations are resolved via the cross-module relationship IDs that we extract and map during the extraction phase. Note that Pipedrive has storage limits by plan tier; we flag attachment-heavy migrations for storage planning before migration.

Sunbase Invoices including repeat invoices and financing-related billing migrate as structured data (not as native Invoice objects, since Pipedrive does not include a full invoicing object in base plans). We extract invoice line items, payment status, and linkage to the originating Project or Client. Invoice data maps to a custom field group on the parent Deal, with line item details preserved as a formatted text field or as linked Product records. Paid invoice history is preserved as Deal Activity notes for audit trail purposes.

Sunbase supports custom fields within most objects, but the field definition metadata (field name, type, validation rules, display order) is not exported alongside the data. We extract field values from each module export but cannot auto-create the destination schema. During scoping, we require a custom field manifest from the customer listing each Sunbase custom field name, object, and data type. We pre-create custom fields in Pipedrive before data migration so that values land in correctly-typed destination fields. Pipedrive's custom field limits vary by plan (Lite has lower limits than Advanced and above); we verify plan tier eligibility during scoping.