Migrate from Comarch Field Service Management to Pipedrive

Comarch work orders are the core record type — they contain job status, assigned technician, site, parts used, time entries, and SLA metrics. We map the work order as a Pipedrive Deal, carrying over the work order title as the deal name, total value (labor + parts), current status as a pipeline stage value, expected or actual completion date as the close date, and the technician email as the deal owner.

Comarch stores customer records with name, address, contact persons, and site locations. We map these directly to Pipedrive Organizations. Each Comarch site address becomes a separate Organization address field or an address custom field depending on how Comarch structures multi-site accounts.

Comarch links contact persons to work orders. We map these to Pipedrive Persons, linking them to the target Organization. Multiple contacts per work order are linked to the same deal via Pipedrive's deal-person association. If a contact already exists in Pipedrive (matched by email address or name), we merge records to avoid duplicates. Any new contacts are created during migration and associated with both the Organization and the relevant Deal record for complete traceability.

Comarch technicians are field resources with skills, territories, and schedules. We match technician email addresses to Pipedrive users by email. Unmatched technicians are flagged — their historical work orders still migrate but are assigned to a fallback owner. Active Comarch technicians who will use Pipedrive must be invited to the Pipedrive account before migration.

Comarch time entries on work orders — labor hours, arrival/departure timestamps, travel time — migrate as Pipedrive Activities. Call activities represent phone-based service interactions; meeting activities represent onsite visits; task activities represent completed work steps. Original timestamps and duration are preserved.

Comarch tracks parts consumed per work order with SKU, quantity, and unit cost. Pipedrive has no native parts-inventory object. We create a parts list as a structured custom field on the Deal (text field with line-item format) or as multiple custom fields (part_name, quantity_used, unit_price) — your admin chooses the format before migration runs.

Comarch asset records link installed equipment to customer sites with serial numbers, maintenance history, and warranty status. Pipedrive has no native asset object. We map key asset fields (equipment type, serial number, last service date, warranty expiry) as custom fields on the Organization record, preserving traceability for field teams referencing the record post-migration.

Comarch enforces SLA timers on work orders (response time, resolution time, escalation thresholds). Pipedrive has no native SLA construct. We preserve SLA tier name, target response hours, and target resolution hours as custom fields on the Deal for reference — SLA enforcement must be rebuilt in Pipedrive's Workflow Automations or handled via a third-party SLA tool.

Comarch work order notes and attached documents (photos, signatures, checklists) migrate to Pipedrive Notes attached to the Deal and Files uploaded to the Deal. Text notes are preserved as Pipedrive Note objects linked to the deal, maintaining original formatting where possible. Binary attachments such as images, PDF documents, and signed forms are uploaded to the Deal's file section. File size limits follow Pipedrive's per-plan storage limits, and any files exceeding plan limits are flagged for manual retrieval or alternative storage. The migration log tracks all uploaded file references for audit purposes.

Comarch's AI-driven scheduling engine, route optimization, and real-time dispatch are FSM-specific capabilities with no Pipedrive equivalent. Dispatch plans and schedule assignments cannot migrate. We export the scheduling data as a structured reference file for re-implementation in your chosen field-service or scheduling tool post-migration.

Comarch FSM often extends into Comarch ERP for billing, contracting, or project management. Any custom ERP objects linked to FSM records need to be mapped individually — we create custom fields on the corresponding Pipedrive object and flag any object with no clear destination as a custom field blob for manual review.