Migrate from MobiWork to Pipedrive

MobiWork stores customers and prospects in a single entity with name, company name, email, phone, address, and billing fields. FlitStack splits these into Pipedrive Person (name, email, phone) and Organization (company name, address) records, linked via the Person-Organization relationship. The primary address on the MobiWork customer maps to the Organization's address; the billing address is preserved as a custom text field on the Organization.

The Work Order is MobiWork's core entity — it holds technician assignment, service address, status, description, form fields, and line items. FlitStack maps Work Order to Pipedrive Deal, using the Work Order status to set the deal stage. Technician name becomes a custom field (Technician_Name__c), service address becomes a text custom field (Service_Address__c), and the work description is stored in the deal's custom description field. Work Order line items map to Products linked to the deal via deal_products.

MobiWork quotes include line items, total amounts, tax, discounts, and expiration dates. FlitStack converts quotes to Pipedrive Deals using the Quote Total as the deal value and preserving the expiration date and quote status as custom fields. The quote ID is stored as a custom field for traceability back to MobiWork. Line items become Pipedrive Products linked to the deal.

MobiWork's Parts & Services Catalog maps 1:1 to Pipedrive Products. Fields including name, SKU, description, unit price, and cost map directly to Pipedrive's product_name, code, description, prices, and cost fields. Inventory quantities from MobiWork's Premier-tier inventory module are stored as custom fields on Pipedrive Products since Pipedrive does not track real-time stock by default.

MobiWork's scheduling and dispatching data attaches to work orders as appointment dates, time windows, and assigned technicians. FlitStack converts these to Pipedrive Activities: Tasks for individual to-do items and Events for scheduled appointments. The technician name and appointment window are stored as custom fields on the activity. Note that MobiWork's route-planning and GPS optimization data has no equivalent in Pipedrive and is not migrated.

MobiWork stores both a service address and a billing address on customers. FlitStack maps the service address to the Organization's primary address in Pipedrive. The billing address, which MobiWork uses for invoice delivery and payment processing, is stored as a custom text field (Billing_Address__c) on the Organization record since Pipedrive does not have a separate billing-address construct.

MobiWork work orders carry electronic form data including signature captures and pictures attached to each job. Pipedrive supports file attachments on deals and persons via its Files model. FlitStack downloads all form attachments from MobiWork and re-uploads them to the corresponding Pipedrive Deal as files. Signature image URLs are preserved as a custom field (Form_Signatures_URL__c) for reference. The rich structured form-field data (key-value pairs from digital forms) is stored as a JSON-formatted custom text field on the deal.

MobiWork's Advanced and Premier tiers include Recurrent Services and Service Contracts — agreements that generate recurring work orders on a schedule. Pipedrive has no native recurring-contract entity. FlitStack migrates service contracts as Deals with a custom field (Contract_Type__c) set to 'Recurring' and the recurrence schedule stored as a text field (Recurrence_Schedule__c). Your Pipedrive admin can then use workflow automations to trigger new deals or tasks on the defined schedule.

MobiWork captures payments via Clearent and Stripe integrations, with progressive billing and batch payment support tied to work orders and invoices. Pipedrive has no native payment or invoice entity. FlitStack stores payment status, last payment amount, and payment processor (Clearent or Stripe) as custom fields on the corresponding Deal. Invoice records from MobiWork are preserved as PDF downloads and linked to the deal as files. Payment processing must be reconnected in Pipedrive via your payment processor's integration.

MobiWork users include office staff, dispatchers, and field technicians. Pipedrive has a User object representing each account seat. FlitStack resolves MobiWork owner and technician IDs to Pipedrive Users by email match. Unmatched technicians are flagged as a pre-migration action item — your team either creates Pipedrive users for them or assigns their records to a fallback owner before the migration runs.

MobiWork work order statuses (e.g., Scheduled, In Progress, On Hold, Completed, Cancelled) map to Pipedrive deal stages via a value-by-value mapping. FlitStack creates a Pipedrive pipeline whose stages match the MobiWork status vocabulary. Stage-entered timestamps are preserved as custom datetime fields (Work_Order_Status_Set__c) on the deal so historical status-transition timing is available in Pipedrive reporting.

MobiWork's Premier-tier inventory module tracks parts stock levels by location. Pipedrive Products have no native inventory field. FlitStack stores stock quantity, reorder point, and last-updated timestamp as custom fields on each Pipedrive Product (Inventory_Qty__c, Reorder_Point__c, Inventory_Updated__c). Real-time stock synchronization requires a third-party inventory integration — your team should evaluate Pipedrive Marketplace apps or a custom API connector.

MobiWork Projects group multiple work orders under a single client project with crew assignments and billing aggregation. Pipedrive has no native project entity. FlitStack migrates Projects as a custom text field (Project_Name__c) on each related Deal and stores the project-level billing aggregate as a custom field (Project_Total__c). Your Pipedrive admin can use deal grouping by this field for project-level reporting.

MobiWork Crews group multiple technicians for complex jobs. Pipedrive has no native crew concept. FlitStack stores the crew name as a custom field (Crew_Name__c) on the deal and assigns the crew lead as the Pipedrive User. Individual crew member names are stored as a comma-separated custom text field (Crew_Members__c) on the deal.

MobiWork's Premier-tier time tracking records labor hours against work orders by technician. Pipedrive Activities have a duration field but no native time-tracking structure. FlitStack converts time entries to Pipedrive Activities with start/end times and the hours worked stored as custom fields (Hours_Worked__c, Technician_Rate__c, Time_Entry_ID__c) on the activity record.