Migrate from ServeManager to Pipedrive

GPS proof-of-service data has no native Pipedrive field

ServeManager captures GPS latitude and longitude per attempt as court-admissible proof of service. Pipedrive has no native geolocation or map field on Activities — GPS coordinates migrate as two custom number fields (Latitude__c, Longitude__c) that display as text in the Activity detail view. If your jurisdiction requires GPS proof to be embedded in affidavit PDFs, those PDFs must be exported from ServeManager and attached as Deal Files; the raw coordinate data alone does not auto-populate affidavit documents in Pipedrive. Courts that accept digital GPS logs as evidence require the exported PDF with coordinates embedded, not the CRM field values.

Invoice and payment records require custom field reconstruction

ServeManager tracks invoices and payments as separate objects with their own status, amounts, and Stripe transaction IDs. Pipedrive has no native billing or accounts-reivable object — invoice amounts map to Deal value, invoice status becomes a custom pick-list field, and full payment history is stored as Activity notes or custom fields. If you rely on ServeManager's invoice aging report, that report must be rebuilt in Pipedrive's Insights or exported to a spreadsheet. Stripe fees (2.9% + 30 cents per transaction) calculated by ServeManager are not preserved in migration — those need to be recalculated from Stripe transaction records post-migration if needed for cost analysis.

Job-to-attempt parent-child relationship maps via Activity linking

ServeManager's data model treats Attempts as line items under a Job — each attempt has its own timestamp, GPS, server, and outcome. Pipedrive Activities are linked to Deals individually but the parent-child hierarchy is implicit via the deal link rather than explicit. This means Pipedrive's Activity list view for a Deal shows all attempts in chronological order, but the attempt sequence number from ServeManager is not automatically enforced in Pipedrive's UI. If your workflow depends on a strict Nth-attempt numbering enforced in ServeManager, you need to set that expectation in Pipedrive's automation rules post-migration — FlitStack preserves the attempt_number field as an Activity subject prefix, but Pipedrive does not natively enforce sequential attempt workflows.

ServeManager Stripe integration fees are not preserved in migration

ServeManager charges 2.9% + 30 cents per transaction via Stripe integration, and this fee model is built into ServeManager's invoice records. Pipedrive has no native payment processing — invoice and payment records migrate as data (amount, date, Stripe transaction ID) but the per-transaction fee calculation is lost. If you use ServeManager's built-in Stripe fees for client billing reconciliation, you must pull the original Stripe transaction records from Stripe's dashboard post-migration. FlitStack migrates the Stripe transaction IDs as a custom field on Deals so you can match migrated records to Stripe data, but the fee math is not replicated in Pipedrive.

Pipedrive's token-based API rate limits affect migration tooling

Pipedrive introduced token-based rate limits in December 2024 that throttle API requests per token. Large migrations pulling Jobs, Attempts, Companies, Invoices, and Payments from ServeManager's CSV exports and writing to Pipedrive via API must respect these rate limits. FlitStack AI paces migration writes and handles 429 Too Many Requests responses with automatic retry, but the migration clock time for high-volume datasets extends accordingly. Migrations exceeding 25,000 total records should plan for a longer batch window.