Migrate from Factoreal to Pipedrive

Factoreal Contact records map to Pipedrive Person. The primary email, phone, name fields, and all standard profile attributes transfer directly. We use the Person email as the dedupe key during import. Any Factoreal contact without a valid email is flagged in a reconciliation report and imported with a placeholder email domain that the customer's admin resolves before production cutover.

Factoreal has no native company object; organizations are implied by email domain or stored as custom fields on Contact. We extract domain-based organization groupings during preprocessing, create a matching Pipedrive Organization record for each distinct domain cluster, and attach the Person record to the Organization via the organization_id reference. This reconstruction is essential for meaningful Pipedrive reporting by company.

Factoreal Segments are defined by filter rules on contact attributes and behavioral events. We capture the full segment definition logic during discovery and reproduce equivalent Pipedrive Person Filters (static or dynamic) that replicate segment membership in the destination. Static segment membership migrates as a Person custom field; dynamic segments become saved filter views that refresh as new contacts are added.

Factoreal Campaigns hold subject, content, send history, and engagement metrics. We map campaign metadata to Pipedrive Activity records of type Note, capturing campaign name, send date, open rate, click rate, and delivery status as custom fields on the Activity. Open and click metrics are preserved as numeric fields on the Person record for reporting. Actual campaign email content migrates as HTML blobs stored in Pipedrive note attachments.

Factoreal automation workflows define trigger conditions and multi-step action sequences across email, SMS, and WhatsApp channels. These workflows are not stored in an exportable, portable format. We document the full workflow graph — trigger type, conditions, delays, and each action step — in a structured handoff document so the customer's Pipedrive admin can rebuild equivalent automations using Pipedrive Workflows and Automation rules post-migration.

Factoreal email templates include HTML content and dynamic merge field placeholders. We extract template HTML and identify merge field syntax. Merge field placeholders are converted to Pipedrive's template token format during extraction. Visual rendering differences between Factoreal's email builder output and Pipedrive's template system are documented; the customer reviews each template post-migration before activating it in Pipedrive automations.

Factoreal captures order records with line items, product SKUs, amounts, and timestamps natively. We split each Factoreal order into a Pipedrive Deal record (with order total as deal value) plus a custom field set capturing order ID, order date, and line item summary as a text area. Product SKUs are mapped to Pipedrive Products where possible, or stored as a custom field for integration with an e-commerce connector post-migration.

Factoreal SMS and WhatsApp message history exports as part of campaign and contact data. We extract send timestamp, direction (inbound/outbound), channel, and message content. Each message maps to a Pipedrive Activity record of type Note with the channel noted in a custom field, preserving the conversation timeline on the Person record. Full conversation threading is not preserved in Pipedrive's native activity model; we document this limitation during scoping.

Factoreal contacts carry multiple tags that define audience segmentation and behavioral flags. We export the full tag list per contact and create equivalent Pipedrive Labels during migration. The many-to-many relationship between Person and Label is preserved. If a contact carries a large number of tags (over 20), we consolidate lower-frequency tags into a single compound-label format to stay within Pipedrive's label limits.

Factoreal supports custom fields on contact records. We identify all custom field definitions during the discovery phase, export their values per record, and create equivalent custom fields in Pipedrive using the closest matching field type (text, number, date, dropdown). Pipedrive field type constraints may require some Factoreal multi-select or complex conditional fields to become text fields with a documented format; this is flagged during scoping.

Factoreal users referenced on contacts and campaigns are resolved by email against Pipedrive Users. We extract all distinct user references from export batches and match them to Pipedrive User records. Any Factoreal user without a matching Pipedrive User is held in a reconciliation queue; the customer's Pipedrive admin provisions the missing user before record import resumes.

Factoreal engagement events (emails, calls, meetings, tasks logged within the platform) migrate to Pipedrive Activity records. We map the engagement type to the corresponding Pipedrive Activity subtype (call, meeting, task, note), preserve the timestamp as ActivityDate, and link each Activity to the resolved Person and Organization via the Person's id and the Organization's id. Notes with embedded HTML content are stored as Pipedrive note attachments.