Migrate from Sunbase Data to Zoho CRM

Sunbase Leads (captured via door-to-door forms, web capture, or manual entry) map directly to Zoho CRM Lead records. Lead source, status, and assignment data migrate as data fields. Some Sunbase lead fields are tied to automation workflows that cannot migrate; we document these as part of the automation inventory deliverable. The Zoho Data Migration Wizard auto-maps standard lead fields and prompts for custom field creation when it encounters unmapped columns.

Sunbase Contact records (name, email, phone, address, and industry-specific fields depending on CRM module configuration) map to Zoho CRM Contact. We preserve all standard fields and map custom contact fields to Zoho custom fields created during the migration wizard phase. The customer provides a custom field manifest during scoping so field types match correctly.

Sunbase Client records represent business entities (companies) that Sunbase distinguishes from individual Contacts. We map Client to Zoho CRM Account, preserving business name, address, and any client-level custom fields. Account becomes the parent of the related Contact records, establishing the Account-Contact hierarchy that Zoho CRM uses for organizational modeling.

Sunbase Deals track the full sales cycle including proposals, quotes, and pipeline stages. We map Deal to Zoho CRM Deal, preserving deal values, stage history, and associated contacts. Pipeline stage names and deal statuses migrate as data values. Custom deal fields require explicit mapping against Zoho custom fields, and the customer provides the custom field manifest during scoping.

Sunbase Projects represent installation or job-site operations with no direct standard equivalent in Zoho CRM. We create a Zoho custom module named Projects (auto-detected from Projects_C.csv naming or manually mapped during wizard configuration) and migrate project metadata, status, budget tracking, and linked Work Orders as a unified record. Projects with multiple associated Work Order records are linked via Zoho lookup fields after both modules are created.

Sunbase Work Orders include permit info, task details, attachments, and system specifications. We create a Zoho custom module Work Orders linked to the Projects custom module via a lookup field. Employee assignments and scheduling data migrate as related records or custom fields. Attachments migrate as Zoho CRM file attachments linked to the Work Order record. Zoho's attachment limit and file size constraints apply per the target edition.

Sunbase generated invoices including repeat invoices and financing-related billing map to Zoho CRM Invoice. We extract invoice line items, payment status, and linkage to the originating project or client. Historical paid invoices migrate with their status preserved. Zoho Invoice module supports custom fields so industry-specific billing data maps without truncation.

Sunbase Employee records include HR data, crew assignments, and role information. Zoho CRM Users represent licensed platform users; non-licensed employees who do not log into Zoho migrate to a custom Employee module with their HR data stored as fields. GPS location history is bulk-exported where available and mapped to a Zoho custom field or related record. The customer decides during scoping whether to provision employees as Zoho Users (if they need CRM access) or a custom HR module.

Sunbase Appointments sync with Google Calendar and include customer-linked scheduling. We preserve appointment dates, times, assigned contacts, and status as Zoho CRM Event records for calendar-linked appointments or Task records for to-do style appointments. Calendar linkage itself is not transferable; appointments land in Zoho's activity timeline linked to the parent Contact or Account record. Recurring appointment patterns do not migrate as recurring definitions; they are resolved into individual Event records.

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, Project, Work Order). Each file is attached to its Zoho CRM record via the Attachments module. The Attachments folder must be zipped alongside CSV data files per Zoho's migration wizard structure, and individual file size limits apply per the target Zoho CRM edition.

Sunbase Asset and Inventory records track materials, equipment, and supplies across projects. Equipment and inventory items with SKU and pricing data map to Zoho CRM Product records if they appear in the sales quoting context. Standalone asset tracking records (without pricing context) map to a custom Asset module created during migration. Quantities, linked projects, and supplier information migrate as custom fields. Inventory levels at the time of migration are preserved as snapshot values rather than live inventory sync.

Sunbase supports custom objects within its module system but provides no documented export schema for custom object definitions. We cannot guarantee complete migration of custom object definitions without a customer-provided manifest. We create Zoho custom modules for identified custom objects (using _C.csv naming if available) and migrate data values. The customer provides the custom object field manifest during scoping, including field names, types, and any picklist values, so Zoho custom fields are created with correct types before data import begins.