Migrate from Force24 to Pipedrive

Force24 Contacts map directly to Pipedrive People. All standard fields (first_name, last_name, email, phone, address) migrate via Pipedrive's Person API endpoint. We preserve lifecycle stage as a custom field on the Person record, and any custom contact properties migrate as additional Pipedrive custom fields. The email address serves as the dedupe key. Active status in Force24 maps to open; unsubscribed contacts set the Pipedrive opt-out flag accordingly.

Force24 Company records (often lightweight — name and URL) map to Pipedrive Organizations. We preserve the association by writing the Organization first, then resolving the org_id on each related Person record during Person import. HubSpot-style domain-based dedupe applies where Force24 contacts share a company domain.

Force24 stores Leads as Contacts with a lifecycle stage property. We evaluate each Contact's lifecycle stage at migration time. Contacts with early-stage values (subscriber, lead, marketing qualified) are migrated as Pipedrive Leads. Contacts with later-stage values (sales qualified, customer, evangelist) are migrated as Pipedrive People attached to an Organization. We preserve the original Force24 lifecycle stage as a custom field on both record types for reporting continuity.

Force24 tracks email opens, clicks, and delivery status against contacts. These engagement events migrate to Pipedrive Activity records with type=email, the original Force24 timestamp preserved as the activity date, and the engagement detail (opened, clicked, bounced) stored as activity subject or a custom field. Email content is linked to the Activity record where available.

Force24 SMS and WhatsApp message history migrates to Pipedrive Activity records with type=note or type=call, tagged with a custom activity type field to distinguish the channel. The message content, direction (sent/received), and timestamp transfer. Delivery receipts and status codes are stored as custom fields on the activity.

Force24 form submissions are engagement events that capture contact data at point of entry. We migrate them as Activity records of type=note on the relevant Person record, noting the form name, submission timestamp, and submitted field values where those values add context to the contact timeline.

Force24 Smart Lists save complex filter queries against contacts. We export the segment membership — which contacts are in each list — and recreate it as Pipedrive Static Lists under the People object. The saved filter query itself cannot transfer; we document each Smart List's criteria so the customer can rebuild the dynamic segment in Pipedrive using its filter views. Active real-time segments require manual recreation as Pipedrive does not support saved query-based dynamic lists natively.

Force24 contact tags migrate to Pipedrive Labels. All tags on a contact become labels on the corresponding Person record, preserving the full tag taxonomy. Labels are created during migration if they do not already exist in the destination. The label namespace is flat in Pipedrive; hierarchical Force24 tags flatten into a single label set.

Force24's lead scoring engine assigns numeric scores to contacts based on behaviour and properties. We export the score value stored on each contact and write it to a Pipedrive custom numeric field on the Person record. The scoring rules themselves (point allocations per action) are platform-configured and do not transfer; we document the rule structure for the customer to rebuild in Pipedrive's Goals and KPI tools or a third-party scoring integration.

Force24 Custom Objects (e.g., Bookings) are linked-data tables activated by account manager. We export each Custom Object definition and all associated records via the Force24 API (coordinated with their technical team), then re-link them to the migrated Person record using a lookup reference. In Pipedrive, Custom Object records are stored as Activity records of type=note with a custom activity type field, or as custom fields on the Person if the object schema is simple. This step requires confirming whether Custom Objects are active on the Force24 account before export, as inactive Custom Objects are invisible to the API.

Force24 distinguishes Marketing and Sales users with different seat pricing. We extract all users referenced on contacts, activities, and custom object records, and map them to Pipedrive Users by email match. Any Force24 user without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Force24 users map to inactive Pipedrive users to preserve historical assignment.

Force24 email templates are platform assets with Force24-specific merge fields. We do not migrate them as functional templates because merge field syntax does not transfer. We export templates as HTML files if the customer wants to repurpose the layout in Pipedrive's email tool or a third-party email platform. The customer reviews and adapts the HTML for their new email sending tool.