Migrate from Sunbase Data to Freshsales

Sunbase Contact records (name, email, phone, address, and any industry-specific fields) map to Freshsales Contact. We preserve standard fields directly and carry custom field values into Freshsales custom fields on Contact, assuming a field manifest has been provided during scoping. Sunbase contact-to-deal relationships are preserved via the Deal mapping and resolved at migration time through the parent contact ID.

Sunbase Leads capture door-to-door and web-sourced prospects with lead source, status, and assignment fields. We map these to Freshsales Lead with the original Sunbase lead source preserved in a custom field. Lead scoring logic (if configured in Sunbase) does not migrate; we document it for the customer to rebuild in Freshsales Freddy AI or a workflow rule.

Sunbase Deals track the sales cycle including proposals, quotes, and pipeline stages. We map deal amount, stage name, stage history, and associated contact references to Freshsales Deal. Pipeline stage definitions migrate as data values only; the visual pipeline board requires manual configuration in Freshsales. Custom deal fields map to Freshsales custom fields on Deal with a type validation step before import.

Sunbase Projects represent installation or job-site operations and carry project metadata, status, budget, and work order linkage. We assess whether each Project functions primarily as a customer account (for long-term client records) or as a project opportunity (for active jobs with a financial value). Projects with a budget and active financial tracking map to Freshsales Deal with project metadata stored as custom fields. Projects with a client-relationship function map to Freshsales Account with project-specific fields. This split is determined during scoping with the customer.

Sunbase Work Orders include permit information, task details, system specifications, and employee assignments. We carry Work Order data as a related record or as additional fields on the parent Deal (from the Project mapping). Attachment files within Work Orders migrate as Freshsales file attachments linked to the parent record. Permit status and system specification fields map to Deal custom fields.

Sunbase Invoices include line items, payment status, and linkage to the originating Project or Client. We map invoice line items to Deal product items in Freshsales and payment status to a custom picklist field on the Deal. Historical paid invoices carry over as closed-won Deals with the invoice amount preserved. Outstanding invoice status is mapped to a custom field for the customer's finance team to reconcile.

Sunbase Employee records contain HR data, crew assignments, and role information. We map active Sunbase employees to Freshsales User records by matching email. Employees without an email or who are not intended as CRM users are mapped to a custom object or held for the customer's admin to assign CRM roles. GPS location history from Employee records migrates as a custom object or as notes on the User record depending on the customer's reporting needs.

Sunbase Appointments carry scheduling data, assigned contacts, dates, times, and status. We map these to Freshsales Task records with ActivityDate set to the Sunbase appointment date and description carrying the original scheduling details. Google Calendar synchronization (if configured in Sunbase) does not transfer; Freshsales calendar sync is configured separately post-migration. Appointment status migrates as a custom picklist value on Task.

Sunbase Documents include contracts, permits, and financing applications stored within the platform. We extract binary files with their original file names and upload dates, and attach them to the corresponding parent record in Freshsales (Contact, Account, or Deal). File associations are preserved through the cross-module relationship map built during discovery.

Sunbase custom field values migrate to Freshsales custom fields on the equivalent object. Sunbase does not export field definition metadata (field name, type, validation rules), so we request a custom field manifest from the customer during scoping. We validate types before import to avoid mismatches (for example, date fields stored as text in Sunbase must be parsed and retyped). Industry-specific custom fields like aerial measurement or financing status are mapped to Freshsales custom fields on Contact or Deal.

Sunbase pipeline board configurations, visual stage boards, and automation rules are tied to the internal workflow engine and are not exposed via any export mechanism. We cannot migrate pipeline configurations as functional rules. During scoping, we document the current pipeline stages, automation triggers, and rule logic from the source system. The customer rebuilds pipeline stages in Freshsales using the documented map; automation rules are rebuilt as Freshsales workflows post-migration.