Migrate your Sunbase Data data

Contact records in Sunbase include standard fields (name, email, phone, address) plus industry-specific fields depending on the CRM module configuration. We map each contact to the destination schema and preserve any custom fields added by the customer.

Sunbase captures leads through door-to-door sales forms, web capture, and manual entry. We preserve lead source, status, and assignment data. Some lead fields are tied to automation workflows that may not transfer 1:1.

Deals in Sunbase track the full sales cycle including proposals, quotes, and pipeline stages. We preserve deal values, stage history, and associated contacts. Custom deal fields require explicit mapping during scoping.

Projects represent installation or job-site operations. We carry over project metadata, status, budget tracking, and linked work orders. Projects with multiple associated records are migrated as a unit to maintain data relationships.

Work orders include permit info, task details, attachments, and system specifications. We preserve the full work order record including any linked employee assignments and scheduling data. Attachments are transferred as binary blobs alongside metadata.

Sunbase generates invoices including repeat invoices and financing-related billing. We extract invoice line items, payment status, and linkage to the originating project or client. Historical paid invoices are migrated with read-only financial integrity.

Employee records include HR data, crew assignments, and GPS location history. We preserve employment metadata and role assignments. GPS trail data is bulk-exported where available and mapped to a destination-equivalent field.

Appointments sync with Google Calendar and include customer-linked scheduling. We preserve appointment dates, times, assigned contacts, and status. Calendar linkage is not transferable; appointments land as static records in the destination.

Sunbase supports custom fields and custom objects within its module system, but there is no documented API or export schema for custom object definitions. We cannot guarantee complete migration of custom object schemas without direct database access. We recommend customers document custom field configurations before scoping.

Documents include contracts, financing applications, and permits stored within Sunbase. We extract binary files and preserve file names, upload dates, and associations to the parent record (contact, deal, or project). Document folder structures are flattened during migration.

Sunbase pipeline configurations (visual sales boards, stage definitions, and workflow automations) are tied to the platform's internal workflow engine. These cannot be exported as structured data and are not migrated. We recreate pipeline stage names manually at the destination if requested.

Asset and inventory records track materials, equipment, and supplies across projects. We preserve item names, quantities, linked projects, and supplier information. Inventory levels at the time of migration are carried over; real-time stock data requires a separate handoff process.