Migrate from ServiceMax to Pipedrive

ServiceMax Work Orders map directly to Pipedrive Deals. The work order Subject and Description combine into the Deal name; status values (Open, In Progress, Completed) map to Pipedrive deal stage values via a custom pick-list field on the Deal. Original create dates and owner IDs are preserved as custom fields since Pipedrive overwrites CreatedDate at migration time.

ServiceMax work order status values (Open, Dispatched, In Progress, On Hold, Completed, Cancelled) do not have direct Pipedrive equivalents. We create a custom pick-list field on the Deal record in Pipedrive and map each ServiceMax status value to the closest Pipedrive stage label. Status-changed timestamps become custom datetime fields for audit continuity.

ServiceMax Assets represent physical equipment installed at customer locations. They map to Pipedrive Organizations (the company-level record). The asset name becomes the Organization name, and address information transfers to custom fields on the Organization since Pipedrive does not have a native asset or location object. Asset serial number and model become custom text fields for reference.

ServiceMax Installed Base tracks which assets are installed at which locations — a many-to-many relationship with location context. Pipedrive has no native Installed Base equivalent. We create a custom text field on the Organization record to store the Installed Base reference ID, and surface related assets as linked Organization records with a custom relationship label.

ServiceMax Service Contracts define entitlement coverage, response times, and billing terms for assets. Pipedrive has no native service contract object. We create a Deal record representing the contract with the customer Organization linked, and store contract-specific fields (contract type, start/end dates, coverage level) as custom fields on that Deal. Entitlement business rules must be rebuilt as Pipedrive automations or manual checklists.

ServiceMax Work Order Line Items represent parts, labor hours, or fees attached to a work order. When the line item has a product SKU, we map it to a Pipedrive Product record and link it to the Deal via the Deal-Product association. Time-and-materials entries with no SKU become custom fields on the Deal, preserving the description and quantity.

ServiceMax Entitlements define which customers are covered under service contracts and what SLAs apply. Pipedrive has no native entitlement object. We create custom fields on the Organization record for entitlement name, type (Field, Depot, Onsite), and status (Active, Expired, Pending). Coverage rules must be rebuilt manually or via Pipedrive Automations on Advanced+ plans.

ServiceMax Technical Attributes are structured data templates (refrigerant type, voltage rating, BTU capacity) attached to asset models. Each attribute becomes a custom field in Pipedrive with the matching field type (text, number, date, or pick-list). ServiceMax validation rules and cross-field dependencies on Technical Attributes do not transfer — those must be rebuilt as Pipedrive automation rules or manual review processes.

ServiceMax attachments on work orders (photos, PDFs, inspection reports) are downloaded from Salesforce Files and re-uploaded as Pipedrive Deal attachments. File size limits match Pipedrive's attachment limits. Inline images in ServiceMax notes are extracted, rehosted if needed, and stored as file references in Pipedrive Notes attached to the Deal.

ServiceMax technicians and dispatchers map to Pipedrive Users by email address. Skills, certifications, and service territories stored as custom fields on the Pipedrive User record. SFM Mobile Permission sets and configuration profiles in ServiceMax have no Pipedrive equivalent — those access-control concepts do not apply in Pipedrive's simpler user model.