Migrate from Service Toolz to Pipedrive

Work orders must become Pipedrive deals with custom fields — there is no native work order object in Pipedrive

Service Toolz work orders carry structured fields — service_type, site_address, checklist items, technician assignment — that have no first-class equivalent in Pipedrive. Pipedrive has Deals (Opportunities), People, Organizations, Activities, and Products, but nothing that natively models a job ticket. FlitStack maps each work order to a Deal and stores the service-specific properties as custom fields on that Deal. You will need to decide which Pipedrive pipeline and stage should receive work orders before migration, and which Service Toolz work order statuses map to which Pipedrive stages. If your team relies on the structured checklist format of Service Toolz work orders, those checklists become sequential Tasks on the Deal — your reps will need to adapt to tracking job steps as a task list rather than a structured form.

Activity history loses its structured checklist format when it becomes Pipedrive Tasks

Service Toolz work orders store structured checklist items — each step with a description, a completion flag, and a technician attribution. Pipedrive's Activity model is flat: Tasks are individual to-dos with a subject and a due date, and Events are calendar entries with start and end times. The hierarchical relationship between checklist steps is lost in migration. Each checklist item becomes a standalone Task with a reference back to the Deal. If your team uses Service Toolz checklists to track multi-step job completion (e.g. Step 1: Inspect, Step 2: Repair, Step 3: Test), that sequential context is not preserved in Pipedrive's Task model without custom sorting logic or a custom sub-task structure. FlitStack preserves the checklist order via the Task's sort_order field, but the Pipedrive UI does not natively render tasks as a structured checklist on the Deal record.

Pipedrive's API token-based rate limits require batch sizing during migration

Pipedrive enforces token-based API rate limits: 30,000 base tokens per day multiplied by your plan's seat multiplier. Each API endpoint consumes a different token weight — simple list endpoints consume fewer tokens than full record exports. For migrations with large activity histories (thousands of tasks and events per work order), FlitStack implements batched extraction with backoff logic to stay within your daily token budget. If your Service Toolz instance has a high volume of logged activities, the migration clock time extends because we pace requests to avoid hitting rate limits. This is not a data loss risk — it is a timeline risk that we disclose upfront and manage with pre-migration rate-limit estimation based on your record counts.

Pipedrive users must exist before migration or records are invisible due to visibility groups

Pipedrive's visibility group model means that records owned by users not yet in your Pipedrive workspace are invisible to all users by default — they appear only to the global admin. Service Toolz technicians who are assigned as work order owners but do not yet have Pipedrive accounts will have their records created under a fallback owner (typically the migration admin) unless you create their Pipedrive user accounts first. FlitStack flags all unmatched owner emails before migration and requires you to either invite those users to Pipedrive or designate a fallback owner. This is not a data loss issue — the records migrate — but the owner attribution is affected if the user list is not resolved before the migration runs.

Scheduler and calendar dispatch records do not transfer — the dispatch model is not portable

Service Toolz's Scheduler Integration module links work orders to technician calendars via Google Calendar sync. Pipedrive has no dispatch or scheduling optimization module — activities have calendar sync but no route planning, technician availability, or geolocation-based scheduling. Work order scheduling data (booked time slots, technician assignments, calendar entries) migrates as completed or pending Tasks on the Deal, but the active dispatch calendar does not. If your team relies on Service Toolz dispatch to manage field technician routes and real-time scheduling, that operational model needs to be rebuilt in Pipedrive or handled by a separate scheduling tool post-migration.