Migrate from ForceManager CRM to Pipedrive

ForceManager Company records map directly to Pipedrive Organization. The company name becomes the organization name, and any z_prefix extra fields (z_industry, z_region) are extracted by querying the Fields endpoint during scoping, then recreated as Pipedrive custom fields with human-readable labels. Owner assignment maps from ForceManager's responsible user to Pipedrive's user_id on the organization. Company type and rating are preserved as custom fields or mapped to Pipedrive label fields if applicable.

ForceManager Contact records map to Pipedrive Person objects. Each Person receives a link to the parent Organization via Pipedrive's org_id field. Standard fields (name, email, phone, job title) map directly. Custom z_prefix fields on Contact are extracted during schema introspection, stripped of the z_ prefix, and recreated as Pipedrive custom person fields. Owner assignment resolves by email match against the Pipedrive user table.

ForceManager Opportunities map to Pipedrive Deals. The opportunity stage maps to a Pipedrive Pipeline stage. We pre-create the Pipedrive pipeline and stages based on ForceManager's stage names during the schema phase. Deal value, expected close date, and responsible user migrate directly. Any z_prefix custom opportunity fields are recreated as Pipedrive custom deal fields. Stage history from ForceManager is preserved as deal stage change log entries in Pipedrive if available.

ForceManager field visit activities contain GPS coordinates, visit notes, and linked Contact or Company. We map these to Pipedrive Activity records (type = visit or call depending on activity type in ForceManager) with the original timestamp and location preserved. Detailed visit notes from ForceManager migrate as Note records linked to the parent Person or Organization. GPS coordinates are stored in a custom Pipedrive field if available or noted for manual entry.

ForceManager Tasks map to Pipedrive Activities of type task. Status (open, completed), due date, and assignee migrate directly. Completed task timestamps are preserved as the activity completion date. Open tasks without due dates are flagged in the reconciliation report for the customer to assign dates in Pipedrive.

ForceManager calendar Events (name, date/time, location, attendees) map to Pipedrive Activities of type calendar_event. The start and end timestamps, location field, and linked Contact or Company associations migrate directly. Attendee lists are noted for manual entry in Pipedrive as Pipedrive does not have a native event attendee model.

ForceManager User records are extracted from the /users endpoint. We match each ForceManager user by email to a Pipedrive User. Any ForceManager Owner references on Companies, Contacts, or Opportunities are updated to point to the resolved Pipedrive User ID. Users without a matching Pipedrive account go to the reconciliation queue for the customer to provision before record import.

ForceManager Sales Order and Sales Order Line records do not have a direct Pipedrive equivalent. We map Sales Order data into the associated Pipedrive Deal using custom fields for order number, order date, and line item details. If the customer requires product-level order tracking, we document the Products and Order Lines migration requirement during scoping and recreate them as custom deal fields or separate Product records if the Pipedrive Products feature is enabled.

All ForceManager custom fields carry a z_ prefix in the API payload. We query the ForceManager Fields endpoint during extraction to capture label-to-prefix mappings. We then create Pipedrive custom fields with human-readable labels, matching the field type (text, number, date, dropdown) to the equivalent Pipedrive field type. Pipedrive's field type options (text, varchar, date, double, enum, user) are mapped from ForceManager field types retrieved during schema introspection. Custom fields are created before any data import to avoid schema lookup errors.

ForceManager saved views are documented during scoping. We extract the filter criteria and column configuration from each view and recreate equivalent Pipedrive filters and column preferences. Pipedrive's filter system differs from ForceManager's views, so we document the original filter logic for the customer's admin to configure in Pipedrive during the post-migration setup phase.

ForceManager attachments are not accessible via the public REST API. We flag all records with attachment dependencies during scoping and advise the customer to download files from the ForceManager web UI before the migration window. We cannot automate attachment extraction and cannot guarantee completeness without customer-provided files. Post-migration, the customer uploads attachments to Pipedrive manually or via the Pipedrive API.