Migrate from Accruent Vx Field to Pipedrive

Work orders are not deals — revenue recognition requires a merge step

Accruent Vx Field work orders carry billable amounts, labor hours, and parts costs but do not map 1:1 to Pipedrive Deals. Pipedrive Deals represent a sales pipeline stage, not a service billing event. FlitStack AI's approach is to migrate work orders as Activities first, then merge completed work orders by client and billing period into Pipedrive Deals — with the total billed amount as the deal value and a custom labor-hours field. Teams that expect every work order to appear as a standalone Deal will need to adjust their expectation; the merge step is surfaced in the pre-migration plan so admins can configure the billing-period grouping rule before the full run.

Pipedrive multi-select (set) custom fields require value-by-value mapping

Accruent Vx Field custom fields on work orders and assets frequently use multi-select or set-style pick-lists (e.g., 'Service Category' with values Repair, Installation, Inspection, Emergency). Pipedrive's equivalent is the 'set' field type, which stores values as an array. When migrating, each distinct value from Accruent's multi-select must be mapped to a corresponding Pipedrive set-option. If Accruent uses a custom value not yet created in Pipedrive, the migration pauses and prompts the admin to create the option in Pipedrive's field settings before the import continues. We surface all value-mapping requirements in the pre-migration field inventory.

Pipedrive token-based API rate limits introduced December 2024 constrain bulk import speed

Pipedrive's API introduced token-based rate limits of 100 requests per second per token starting December 2024. Accruent Vx Field exports that contain tens of thousands of work order history records will hit this ceiling during migration. FlitStack AI handles this by batching API writes, implementing exponential backoff on 429 responses, and distributing writes across multiple Pipedrive API tokens when available. For migrations exceeding 200,000 records, the clock time extends beyond the base estimate because the rate limit cap reduces throughput. We measure actual throughput during the sample migration and adjust the full-run timeline accordingly.

Preventive maintenance scheduling and dispatch logic has no Pipedrive equivalent

Accruent Vx Field's core value is its intelligent scheduling engine: meter-based PM triggers, geographic routing, and technician skill matching. Pipedrive has no native scheduling, PM interval, or dispatch optimization module. The scheduling logic cannot be migrated — it must be rebuilt. FlitStack AI exports the PM schedule definitions (frequency, last completed date, asset assignment, interval type) as a structured JSON reference file that can be used to configure Pipedrive Automations or handed to a dedicated scheduling add-on such as Salesforce Field Service, UpKeep, or BuildOps. This is explicitly not included in the data migration scope.

Asset-to-Product mapping loses inventory tracking for consumable parts

Accruent Vx Field tracks parts inventory across warehouses and service vans — stock levels, reorder points, and bin locations. Pipedrive's Products module tracks sellable products with unit price and stock quantity, but it does not support multi-warehouse locations, bin management, or reorder automation. Consumable parts used in service work (replacement filters, connectors, fittings) that were inventory-tracked in Accruent migrate to Pipedrive Products with their last known stock quantity as a snapshot custom field. The ongoing inventory management must run in a separate parts-tracking system post-migration. We flag which parts records have active stock tracking so the team knows what requires a separate system.