Migrate from Salesflo Engage to Pipedrive

Survey responses have no native Pipedrive container — data must be flattened into Notes

Salesflo Engage dynamic survey fields can contain multi-question forms with branching logic, conditional visibility, and varied input types (text, numeric, photo capture). Pipedrive has no native survey or form-response object. FlitStack serializes each response into a Pipedrive Note attached to the linked Person or Organization, with field labels preserved as content prefixes. If a survey contains more than ~131,072 characters for a single submission, it is split across multiple Notes with sequence numbering. Pipedrive's file attachment limits per plan also apply to any photo responses stored as Notes attachments. We validate Note character counts before migration to catch oversized submissions.

Pipedrive token-based API rate limits require batch staggering on large visit-history exports

Pipedrive introduced token-based rate limits in December 2024 that apply per API token rather than per endpoint. For Salesflo Engage migrations with large visit histories (50,000+ activity records), FlitStack staggers API calls into queued batches to avoid 429 responses. Pipedrive's rate limit documentation specifies 100 requests per 10 seconds per token for standard plans, with higher limits available on Enterprise. We monitor response headers and back off dynamically. This adds 15–30% to processing time on large datasets but prevents partial-failure scenarios where some activities are written and others silently rejected.

Visit status requires a custom field since Pipedrive Activities lack granular outcome states

Salesflo Engage tracks visit outcomes with fine-grained states: completed, no-answer, rescheduled, cancelled, bad-location. Pipedrive Activity records support only two status values (done/not done) plus an active flag. There is no native 'outcome' dimension on Pipedrive Activities. FlitStack creates a custom pick-list field 'Visit_Outcome__c' on the Activity object and maps the source status value-by-value. This custom field becomes the reporting dimension for visit success rates in Pipedrive Insights — without it, you can only report on completed vs. incomplete visits, losing the nuanced outcome data that drove field-team coaching in Salesflo Engage.

GPS and location data has no native Pipedrive geo field — stored as custom Number fields

Salesflo Engage's location tagging captures GPS latitude and longitude as first-class fields on visit and location records. Pipedrive has geo_latitude and geo_longitude fields on Organization, but they are populated only for address-based geocoding, not for raw coordinate storage from field devices. FlitStack stores raw GPS coordinates as custom Number fields 'GPS_Latitude__c' and 'GPS_Longitude__c' on the Organization record. Pipedrive's map view will not render these coordinates natively — if your team relies on field-force map visualization, you will need a third-party integration (e.g., Google Maps API or a custom Power BI layer) to plot these custom fields.

Salesflo Engage workflows must be rebuilt from exported definitions — no automation migration

Salesflo Engage workflows define how field tasks are routed, what forms trigger on arrival at a location, and how conditional branching works based on visit outcomes. Pipedrive's Automation engine (triggered by field changes, deal stage transitions, or activity updates) and Pipedrive Sequences (email cadences) are architecturally incompatible with Salesflo Engage's workflow model. FlitStack exports the complete workflow JSON schema including condition logic, branching rules, and form-to-task mappings. This export serves as the blueprint your Pipedrive admin uses to rebuild equivalent Pipedrive Automations. We strongly recommend building the Pipedrive automations in a sandbox or trial account before go-live so the migration does not land in an automation vacuum.