Migrate from MobiWork to Freshsales

Work orders have no Freshsales native equivalent — they require a custom data model

MobiWork work orders are the central record of field service operations, capturing job status, technician assignment, parts consumed, and site details. Freshsales has no Work Order object. We map work orders to Deals and store work-order-specific metadata in custom fields (Work_Order_Status__c, assigned_technician__c, parts_used__c). Before migration, your Freshsales admin must create these custom fields in the CRM settings using underscores for API naming (e.g., Work_Order_Status__c). Without pre-creation, migration validation fails because Freshsales rejects writes to undefined custom fields. This is not a data-loss risk — it is a schema-preparation dependency that must be resolved before the migration run.

Freshsales invoicing is absent — historical invoices become a reference object

MobiWork includes full invoicing with progressive billing, payment capture, and QuickBooks sync. Freshsales does not include an invoicing module at any tier. We preserve historical invoices as records in a Service_History__c custom object linked to the corresponding Deal, storing invoice number, date, total, and payment status. However, Freshsales cannot generate new invoices from this data — that capability requires either Freshsales Suite or a separate accounting integration. Teams migrating from MobiWork should plan to rebuild invoice workflows in a dedicated billing tool and should not expect Freshsales to replace MobiWork's invoicing functionality.

Freshsales API rate limits vary by plan tier — migration throughput is capped

Freshsales enforces API rate limits per account per hour: Growth plan caps at 1,000 requests per hour, Garden/Estate at 2,000 per hour, and Forest at 5,000 per hour. A bulk migration of 50,000 work order records with associated activities can exhaust Growth-tier limits and trigger 429 Too Many Requests responses. We throttle API calls to stay within plan limits and use exponential backoff with retry logic. If your record volume exceeds what your plan tier can absorb in a reasonable window, you may need to upgrade to a higher Freshsales plan before migration runs or split the migration across multiple days with delta pickups.

Scheduling and dispatching data cannot map to Freshsales calendar or tasks

MobiWork's scheduling engine stores technician assignments, time windows, route sequences, and dispatch notes. Freshsales has no scheduling or dispatching model — its calendar view shows Events tied to Contacts or Deals but does not support multi-technician routing, availability blocking, or job-site routing. We map scheduled work order dates to Deal close dates for pipeline reporting and map technician assignments to custom fields on Deals. Actual scheduling logic, route optimization, and crew assignments have to be rebuilt in Freshsales via third-party scheduling integrations or abandoned as operational processes.

MobiWork workflows and automations require manual rebuild in Freshsales

MobiWork workflow rules trigger on work order status changes, customer creation, payment receipt, and schedule updates. Freshsales basic Workflows (Growth plan) support record-triggered automation on Leads, Contacts, Accounts, and Deals. Advanced Workflows and Sales Sequences require the Pro plan. Workflow definitions are not transferable between platforms — each rule must be recreated manually in Freshsales' automation builder. We export a JSON representation of your MobiWork workflow definitions as a reference document for your Freshsales admin to use during the rebuild phase.