Migrate from FRONTU to Pipedrive

Pipedrive has no native field-service schema — job data must be force-fit into the Deal object

Frontu's Job object tracks service requests with scheduling, asset, location, and technician data. Pipedrive has no job or work-order object — Jobs must map to Deals, and the field-service attributes must become Pipedrive custom fields. Pipedrive's Deal object is optimized for sales-close workflows, not service-dispatch tracking. Scheduling windows, asset IDs, and access instructions that live naturally in Frontu require explicit custom field creation in Pipedrive before migration. If your team relies on Frontu's scheduling board for daily dispatch, that workflow has no Pipedrive equivalent and must be rebuilt using Activities, calendar integrations, or a marketplace scheduling tool.

Frontu job status values require value-by-value mapping to Pipedrive pipeline stages

Frontu tracks job lifecycle with status values like Open, Assigned, In Progress, Completed, and Cancelled. Pipedrive stages are pipeline-scoped string values with no universal semantic — a stage named 'Won' in one pipeline means something different from 'Won' in another. Migrating job_status requires mapping each Frontu status value to a specific Pipedrive stage name within each destination pipeline, and the mapping must be validated per pipeline. If Frontu's status values span multiple Pipedrive pipelines (for example, separate pipelines for installation vs. repair), each pipeline's stage set requires its own value-mapping workbook. Pipedrive's API does not expose a 'universal stage' concept — stage IDs are pipeline-specific UUIDs, so the migration tool must resolve the correct stage_id per Deal based on the pipeline assignment.

Pipedrive token-based API rate limits require throttling during large migrations

Pipedrive introduced token-based API rate limits in December 2024 that affect both new and existing accounts. The rate limit tiers vary by Pipedrive plan — higher-tier accounts receive higher daily and per-minute quotas. During a migration with 10,000+ records and multiple API calls per record (custom fields, activities, file uploads), the migration tool must implement request throttling and respect Pipedrive's 429 Too Many Requests responses. Import2's free tier covers up to 1,000,000 records but imposes its own rate constraints. FlitStack AI monitors rate limit headers in real time and backs off automatically, but large Frontu migrations with extensive activity history may extend beyond the typical 48–72 hour window due to throttling.

Asset and equipment data has no Pipedrive home and must be stored as custom fields

Frontu's Asset records (serial number, make, model, service history, warranty dates) serve as the equipment registry for field operations. Pipedrive has no native asset or equipment object — even on Enterprise plans, asset tracking requires custom objects or third-party marketplace apps. During migration, equipment data can be stored as Pipedrive custom fields on the Deal (linking the asset to a specific job) or on the Organization (linking the asset to a customer account). However, Pipedrive's custom fields are limited to the objects they are created on — a single asset referenced across multiple jobs must be duplicated or cross-referenced manually. If asset tracking is a core operational requirement post-migration, a dedicated asset-management tool outside Pipedrive should be evaluated.

Scheduling and route planning data cannot migrate and must be rebuilt

Frontu's scheduling board, technician route assignments, calendar blocks, and time-slot reservations are operational constructs built on the FSM data model. Pipedrive has no native scheduling, dispatch, or route-optimization module. Time-slot data from Frontu's Job records can be stored as Pipedrive Activity due dates, but the scheduling logic (which technician goes where at what time, optimized routing, buffer between jobs) has no equivalent in Pipedrive. If your team uses Frontu for daily technician dispatch, that workflow must be rebuilt using Pipedrive Activities, a third-party scheduling integration, or a separate FSM tool. We can export the scheduling data (job dates, technician assignments, location coordinates) as a reference CSV for your admin to use when rebuilding the schedule in Pipedrive.