Migrate from MobileWorker to Pipedrive

mobileWorker stores field technicians as named records with contact details, skills, and certification fields. FlitStack maps the primary technician contact to a Pipedrive Person record — the worker's email, phone, and name become the Person's standard fields. Custom certification or skill-code fields on the worker record migrate as Pipedrive custom fields on the Person object.

The customer or account record in mobileWorker — the entity receiving field service — maps directly to a Pipedrive Organization. The Organization's name, address, industry, and phone pull from the source account record. If mobileWorker stores multiple service sites per customer as separate records, each site becomes its own Organization with a parent-child link preserved via a custom field, or all sites roll up to a single Organization per your specified rule.

mobileWorker work orders are the primary operational record — they contain the job description, status, priority, assigned worker, scheduled date, and site reference. FlitStack maps work order headers to Pipedrive Deals: the work order title becomes the Deal name, the estimated or billed amount maps to Deal value, the status code (Open, In Progress, Completed, Cancelled) maps to a Pipedrive stage within your defined pipeline, and the scheduled date maps to the expected close date. Custom work-order fields (e.g., service type, priority level, equipment used) become Pipedrive custom fields on the Deal.

When a single work order contains multiple line items or service tasks, FlitStack merges these into the parent Deal record using a custom field format (e.g., 'Service Tasks: Task 1 | Task 2 | Task 3') or a Products attachment on the Deal. Pipedrive's native Products feature can alternatively be used to create a Product record per service type and link it to the Deal via Deal-Product association — this approach is recommended when line items need individual pricing.

mobileWorker stores site addresses with GPS coordinates (latitude/longitude) as the primary location identifier. Pipedrive's address fields accept formatted street/city/state/postal code/country strings. FlitStack extracts the formatted address into Pipedrive's standard address fields and stores the raw lat/long coordinates as a custom text field (Site_LatLong__c) on the Organization so geo-enrichment tools can re-use the coordinate data post-migration.

Field-service assets and equipment records in mobileWorker map to Pipedrive Products when the asset has a serviceable part number or pricing. If the asset is a non-inventoried piece of equipment tracked for maintenance history, FlitStack creates it as a Product record with a custom field flag (Asset_Flag__c) and stores the asset ID in a custom field (Source_Asset_ID__c) for traceability back to the mobileWorker record.

mobileWorker logs field activities — site visits, equipment inspections, job completions — as timestamped events linked to a work order and a worker. FlitStack maps each activity to a Pipedrive Activity record (type: 'Task' or 'Call' as appropriate), preserving the original timestamp, duration, worker name, and any notes. The activity is linked to the corresponding Pipedrive Deal (from the parent work order) so Pipedrive's timeline view shows the full service history per deal.

Work-order notes and photo attachments from mobileWorker are extracted and re-hosted. Pipedrive Notes are created linked to the target Deal or Person, with the original note text preserved and formatted timestamps included. Photo and document attachments are uploaded to Pipedrive's file storage (respecting Pipedrive's file size limits — 100 MB per file on Enterprise, 25 MB on lower tiers) or stored externally with a URL reference field added to the Deal.

When a work order is dispatched to a specific worker, FlitStack creates a Pipedrive Activity of type 'Task' on the Deal, with the task subject set to the dispatch event, the assigned worker noted in the activity body, and the dispatch timestamp preserved. This gives Pipedrive users visibility into the dispatch history within the deal timeline without requiring a separate dispatch module.

mobileWorker tracks work-order status transitions (e.g., Created → Assigned → In Progress → Completed). FlitStack preserves this history as a sequence of timestamped Activity log entries appended to the Deal's timeline, with each entry noting the previous and new status. For reporting continuity, the original stage-transition timestamps are also stored in custom datetime fields on the Deal.

Any custom fields defined on the Work Order object in mobileWorker — such as service-category codes, billing tier, customer-reference numbers, or regulatory compliance flags — require pre-created Pipedrive custom fields on the Deal object. FlitStack delivers a custom-field creation checklist before the migration run so Pipedrive admins can set up the fields with matching names, enabling auto-mapping on import.

mobileWorker's scheduling and dispatch logic — including availability matching, skill-based routing, and geo-optimized routing rules — has no Pipedrive equivalent and does not migrate. FlitStack exports the current scheduling configuration as a JSON specification document that your Pipedrive admin or implementation partner uses to rebuild equivalent automations using Pipedrive's Automation feature and any third-party scheduling integrations (e.g., Calendly, Chili Piper).