Migrate from Mobile Service App to Pipedrive

Pipedrive has no native field-service or ticket object — Service Pipeline requires schema setup before data lands

Pipedrive does not have a native service-ticket or work-order object. We map your Mobile Service App tickets to Pipedrive Deals using a dedicated 'Service' pipeline, but Pipedrive requires that the pipeline and its stages be created in the UI or via API before import. If the pipeline does not exist, deal imports will fail or land in an undefined state. We deliver a Pipedrive schema setup plan (pipeline name, stage names, stage probabilities) as part of the migration package so your admin can pre-create the structure. Stage order, probability values, and stage labels must be defined per Pipedrive's pipeline configuration interface before the migration run.

Token-based API rate limits introduced December 2024 require batched import sequencing

Pipedrive's API introduced token-based rate limits in December 2024 that cap the number of requests per token per time window. Migrating large record sets requires batching — we space POST and PUT requests across the migration window to avoid 429 Too Many Requests errors. For migrations exceeding 50,000 records, this extends clock time but does not affect data quality. We monitor rate-limit responses in real time and retry with exponential backoff. The rate-limit configuration depends on your Pipedrive plan tier (token quotas vary by Essential through Enterprise).

Custom field hash keys are account-specific and cannot be pre-assigned in migration scripts

Pipedrive custom fields are referenced in the API by auto-generated 40-character hash keys that differ per account. We cannot hardcode these keys in migration scripts. The workflow requires creating custom fields in your Pipedrive account first (so Pipedrive generates the hash keys), then passing those keys to our field-mapping configuration. If your Mobile Service App uses more than 20 custom fields across object types, the setup phase extends by 1–2 days. We provide a custom field creation guide with exact field names, types, and pick-list values for your admin to create before migration day.

Pipedrive Leads and People are separate objects — pre-conversion prospects must be split during migration

Mobile Service App contacts without an active service ticket lack a 'status' that maps natively to Pipedrive's split Lead/Person model. We route records to Pipedrive Leads based on a configurable rule (e.g., no open ticket in the past 90 days) so your sales team can run Lead conversion workflows post-migration. If your source has a mix of leads and active clients, the routing logic must be defined before migration so records land in the correct object. Unconverted Leads in Pipedrive do not appear in standard deal reports — this affects pipeline visibility if routing rules are misconfigured.

Owner resolution by email match is required before migration — unmatched owners create orphaned records

Pipedrive requires a valid OwnerId on Deals. If a Mobile Service App technician or assigned user has no corresponding email-matched Pipedrive user account, their records will land under an admin fallback owner or fail validation. We flag unmatched owner emails in the pre-migration audit and provide a resolution list: invite the user to Pipedrive, reassign records to a designated fallback owner, or exclude the owner field. We do not create Pipedrive user accounts automatically — that requires admin action with appropriate seat licensing. Records with unresolved owners represent a data-integrity risk at go-live if not pre-cleared.