Migrate from Factoreal to HighLevel

Factoreal contacts export as CSV with profile fields, behavioral data, source attribution, and tags. We map first name, last name, email, phone, and custom fields directly to GoHighLevel Contact fields. Tags export from Factoreal as a pipe-delimited string per contact; we split them into GoHighLevel's built-in tag field (comma-separated) and create any missing tag records in GoHighLevel during import. Factoreal contact IDs are preserved in a custom field factoreal_id__c for audit traceability.

Factoreal segments are defined by filter rules on contact attributes and behavioral events. We capture the full segment definition — including field conditions, operators, and event triggers — during discovery and reconstruct it as a GoHighLevel Contact Tag and Smart List combination. Membership is computed at migration time: we evaluate each Factoreal contact against the segment rules and apply the equivalent GoHighLevel tag so the contact appears in the right Smart List without relying on GoHighLevel's native segment event-tracking engine.

Factoreal deals linked to contacts export with deal name, amount, stage, and close date. We map these to GoHighLevel Opportunities, creating a default Opportunity Pipeline if none exists. The Factoreal deal stage maps to a GoHighLevel pipeline stage; we create the stage values during configuration before import. Deal amount and expected close date map directly to GoHighLevel Opportunity amount and close date fields.

Factoreal campaigns hold subject lines, content, send history, and engagement metrics (opens, clicks, replies). We map campaign structure to GoHighLevel Campaigns and preserve open and click engagement data as custom fields on the GoHighLevel Campaign record. Campaign content migrates as a static record; the customer's admin rebuilds send logic in GoHighLevel's Workflow Builder or Campaign tool using the documented send history as reference.

Factoreal email templates include HTML content and dynamic merge field placeholders. We extract template HTML and rewrite merge field syntax to GoHighLevel's format (using {{contact.field_name}}). Visual rendering differences are expected; we flag any conditional content blocks, dynamic images, or AMPscript elements as requiring manual review post-import. Template list migrates as documentation for the customer's admin to validate and republish in GoHighLevel.

Factoreal exports SMS and WhatsApp message logs as part of contact and campaign data, including send timestamps, direction (inbound/outbound), and content. We map these to GoHighLevel Conversations linked to the contact record, with direction and timestamp preserved. Message content migrates as conversation records for reference; GoHighLevel's Conversation inbox structure may differ from Factoreal's layout, so we document the mapping for the customer's admin to verify conversation thread grouping post-import.

Factoreal allows custom fields on contact records. We identify all custom field definitions during discovery, export their values per record, and create equivalent custom fields in GoHighLevel during schema configuration. Field types are mapped: text fields to text, numeric fields to number, date fields to date, and picklist fields to drop-down. GoHighLevel's field type constraints (e.g., phone fields enforce format) may require cleanup on import if source data does not conform.

Factoreal contacts carry multiple tags stored as a per-contact tag list. We export the full tag set per contact and create equivalent tags in GoHighLevel's tag management. Tag-to-contact relationships migrate as GoHighLevel tag assignments on the Contact record. If the customer uses tags for both contact classification and content categorization, we document the tag strategy during scoping and recommend separating contact tags from campaign tags in GoHighLevel's data model.

Factoreal captures order and product data natively. We map order records to a GoHighLevel custom object named Order (created during schema setup) linked to the Contact record. Line items map to custom object records linked to the Order. If the customer uses GoHighLevel's built-in e-commerce features (Stripe integration, product catalog), we map products to GoHighLevel Products and order line items to OpportunityLineItems on the related Opportunity. The customer chooses the structure during scoping based on their post-migration workflow.

Factoreal automation workflows define triggers, conditions, delays, and multi-step actions across channels. These are not exportable in a portable format. We document the full workflow graph — trigger type, conditions, sequence steps, and channel actions — as a written specification. The customer's admin uses this document to rebuild equivalent logic in GoHighLevel's Workflow Builder. Workflow reconstruction is scoped as a separate parallel workstream and is not included in the data migration deliverable.