Migrate from WorkBuddy to Freshsales

WorkBuddy Job is the primary record type in field-service. It maps to Freshsales Deal with the job name as Deal Name, job amount as Amount, job status as Deal Stage (value-mapped), and close date mapped to Close Date. Job type, priority, and site address become custom fields on the Deal.

WorkBuddy customer contacts map directly to Freshsales Contacts. Full name, email, phone, mobile, job title, and address fields translate one‑to‑one. Primary company association migrates as AccountId lookup; additional company associations become Account Contact Relationships. During migration, FlitStack normalizes email addresses (lowercase, whitespace trimmed) to prevent duplicates and validates required Freshsales fields before insert. Any missing mandatory fields are flagged for correction before the contact batch loads.

WorkBuddy leads awaiting job assignment map to Freshsales Leads using the same name, email, phone, and company fields. Lead status maps via value mapping (e.g., 'Prospect' → 'New', 'Qualified' → 'Open - Not Contacted'). Lead source and rating translate to standard Freshsales Lead fields. FlitStack deduplicates leads by email before insert, flags missing required fields, and links the Lead to the migrated Contact record.

WorkBuddy companies map to Freshsales Accounts. Multi-location WorkBuddy companies — where a single entity has multiple branch or site records — require decision: either collapse to one Account with location in custom fields, or split into separate Accounts linked by a Parent Account relationship. FlitStack surfaces this as a pre-migration decision item.

Freshsales has no native Asset object on Growth or Pro plans. On Estate/Forest, Custom Modules handle asset records. For lower plans, asset_serial_number, asset_location, and asset_status migrate as custom fields on the Account or Deal. WorkBuddy asset-to-job associations preserve as custom Deal fields or a junction Custom Module record.

WorkBuddy scheduling records (technician assigned, time window, job site) do not have a Freshsales native equivalent. Mapped as Freshsales Tasks with custom fields for technician_name, scheduled_start, scheduled_end, and site_address. Scheduling board visibility requires Freshsales-side rebuild using calendar views or the Freshworks ecosystem.

WorkBuddy timesheet entries (hours logged per technician per job) map to Freshsales Tasks with custom fields for hours_logged, technician_id, and billable_status. Original timestamps are preserved as task Created Date. WorkBuddy labor cost data can migrate as a custom currency field on the linked Deal. Each task also records the associated WorkBuddy job identifier in a custom Deal field, enabling drill‑down from the Deal to the underlying labor entries.

WorkBuddy safety and compliance records have no Freshsales native equivalent. Migrated as a Custom Module (on Estate/Forest) or as Notes attached to the relevant Job-Deal and Account. Compliance documents stored as attachments re-uploaded to Freshsales Files. Rebuild in Freshsales Compliance modules separately.

WorkBuddy users (technicians, admins, job owners) resolve to Freshsales Users by email match. Unmatched users flagged pre-migration for invitation or fallback owner assignment. Role and permission sets in WorkBuddy do not transfer — Freshsales profile and permission set assignments are configured separately.

WorkBuddy file attachments on jobs and assets are re‑uploaded to Freshsales Files and linked to the corresponding Deal, Account, or Contact record. Original file names and upload dates are preserved for traceability. File size limits depend on your Freshsales plan; any file exceeding the limit is flagged for manual handling. Inline images embedded in notes are extracted and re‑hosted as Freshsales attachments on the mapped record.

WorkBuddy job quotes migrate as line items on the mapped Freshsales Deal if the Products module is configured, or as a custom field capturing the quote total and expiry. Quote templates in WorkBuddy require Freshsales template rebuild via Freshsales email templates or a CPQ add-on.

Freshsales has no native invoice object outside the billing integration tier. WorkBuddy invoices migrate as a Custom Module record linked to the Deal (containing invoice_number, amount, status, and payment_date). Accounting integration with QuickBooks or Xero is configured separately in Freshsales.