Migrate your Factoreal data

Factoreal stores contacts with profile fields, behavioral data, and source attribution. There is no bulk API endpoint documented publicly, so we work from their CSV export format and apply field-level mapping to normalize names, lifecycle stages, and custom properties in the destination.

Segments are defined by filter rules on contact attributes and behavioral events. We reconstruct segment membership logic as filter criteria in the destination CRM, preserving which contacts would qualify rather than storing a static membership list that would drift over time.

Campaigns hold subject lines, content, send history, and engagement metrics. We map campaign structure to the destination's equivalent object (e.g., Programs, Sequences, or Campaigns) and preserve open rates, click rates, and send timestamps as historical activity records.

Automation workflows in Factoreal define trigger conditions and action sequences across channels. We document the full workflow graph — triggers, conditions, and action steps — so the destination platform can rebuild equivalent logic, since automation rules do not transfer as executable code across CRM platforms.

Factoreal templates include HTML content and dynamic field placeholders. We extract template HTML and convert merge field syntax to the destination platform's format, though visual rendering differences between email builders may require post-migration content review.

Website visitor tracking in Factoreal relies on cookie-based session tracking tied to its own javascript embed. These session records are not exportable as structured data and are not portable to other platforms; we document this as a gap in scope during the migration scoping call.

Factoreal's built-in e-commerce integration captures order and product data. We map order records, line items, and product SKUs to the destination's equivalent objects, preserving transaction history and attribution to contact records.

Channel-level message logs are exported as part of campaign and contact data. We preserve send timestamps, direction (inbound/outbound), and content, mapping them to the destination CRM's conversation or activity timeline.

Factoreal allows custom fields on contact and company records. We identify all custom field definitions during the discovery phase, export their values per record, and map them to equivalent custom fields in the destination, handling differences in field type constraints.

Contacts can carry multiple tags in Factoreal. We export the full tag list per contact and create equivalent tags in the destination, preserving the many-to-many relationship across both systems.

Factoreal tracks social campaign engagement metrics. We extract post-level performance data (impressions, engagement, clicks) and map it to the destination's social or campaign analytics records.

Pre-built reports and dashboards in Factoreal are not exportable as transferable artifacts. We export underlying data (contacts, campaigns, engagement events) so the destination can reproduce equivalent reports, but the report configurations themselves do not migrate.