Migrate from MobiWork to Salesforce Sales Cloud

MobiWork Customers (name, company, address, phone, email) split across Salesforce Account (company name, billing address) and Contact (individual name, phone, email). MobiWork site-level addresses map to Account ShippingAddress or custom Site_Location__c fields. When a customer has multiple site locations, each extra site becomes a separate Site__c record linked to the Account, preserving site-specific contact details and ensuring accurate dispatch data.

MobiWork Prospects map 1:1 to Salesforce Leads. Prospect name, company, contact info, and lead source field map to Lead fields. Unconverted prospects remain as Leads; converted prospects become Contacts under Accounts. If a Prospect contains custom fields such as industry classification or rating, those map to custom Lead fields. Duplicate detection uses email address uniqueness to prevent duplicate Leads.

Salesforce has no native work order object in Sales Cloud. We create a custom WorkOrder__c object with fields for work order number, status picklist, priority, scheduled date, assigned technician (User lookup), job site address, and description. Status values map from MobiWork (Scheduled, In Progress, On Hold, Completed) to custom picklist values on WorkOrder__c.Status__c.

MobiWork line items (parts, labor hours, materials) map to a custom WorkOrderLine__c object with fields for product/service name, quantity, unit price, and cost. If the work order is also tracked as an Opportunity, line items map to OpportunityLineItems via PriceBookEntry.

MobiWork Quotes (with line items, pricing, and terms) map to Salesforce Opportunities for basic cases. For complex quote-to-cash workflows, mapping requires Salesforce CPQ — the Quote object and related pricing rules need to be rebuilt since CPQ is a separate product with its own data model.

MobiWork invoices and progressive billing records map to Salesforce Order for basic cases. Complex invoicing requires a custom Invoice__c object with invoice number, line items, payment status, and billing date. Payment records map to a custom Payment__c object or Salesforce Payments (if enabled).

MobiWork technicians resolve to Salesforce Users by email match. Unmatched technicians are flagged before migration. Technician skills, certifications, and availability windows map to custom fields on the User object or a custom TechnicianProfile__c object. During migration, any technician without a Salesforce User account is logged in a resolution report, allowing your team to provision the account or reassign open work orders to a fallback user to avoid data integrity issues.

MobiWork scheduling records (assigned technician, time window, route) map to Salesforce Events for calendar display and to custom fields on WorkOrder__c (ScheduledStart__c, ScheduledEnd__c, AssignedTechnician__c) for data persistence. Route optimization data is text-serialized into a custom field. If your organization uses multi-day scheduling windows or recurring appointment patterns, those details are stored as additional custom fields on WorkOrder__c to support reporting and automation.

MobiWork electronic forms (photos, signatures, PDF attachments) download and re-upload to Salesforce Files (ContentVersion). Each file links to the parent WorkOrder__c record via ContentDocumentLink. Original timestamps and uploader metadata preserved in ContentVersion fields. Files exceeding 25 MB are chunked or stored externally, with a URL reference stored on the WorkOrder__c to maintain accessibility.

MobiWork parts catalog entries map to Salesforce Product2 records. Each product gets a PriceBookEntry in the standard price book. Part cost, markup, and reorder level map to custom fields on Product2 (Part_Cost__c, Reorder_Level__c) since Salesforce does not natively track cost-of-goods.

MobiWork Recurring Services and Service Contracts map to Salesforce Contract for the agreement record, plus a custom RecurringService__c object to store frequency, service scope, and related WorkOrder__c records. Contract status maps from MobiWork contract lifecycle. The Contract record captures the start and end dates, while the RecurringService__c includes the billing interval and linked WorkOrders for service history tracking.

MobiWork Projects and Crews have no Salesforce native equivalent. We create custom Project__c and Crew__c objects with a lookup from Crew__c to Project__c, and from WorkOrder__c to Project__c. Crew members link to User records by email match. The Project__c record stores project name, start date, and status, while Crew__c includes crew size and skill certifications, enabling dispatch planning and capacity reporting.

MobiWork time entries (hours per technician per work order) and job costing totals map to custom TimeEntry__c linked to WorkOrder__c and User. Job costing summaries (labor cost, parts cost, total job cost) map to a custom JobCost__c object on WorkOrder__c.