Migrate from The Customer Factor to HighLevel

The Customer Factor's customer record maps directly to HighLevel's Contact object. All contact-level fields — name, phone, email, address — transfer as direct field mappings. The Customer Factor's prospect flag is preserved as a Contact tag so teams can distinguish pre-conversion leads from active clients in HighLevel.

Prospects in The Customer Factor have the same schema as customers but lack a service history. They migrate as HighLevel Contacts with a Prospect tag. FlitStack resolves any duplicate email matches against existing customers before creating the Contact record. In addition to tagging, FlitStack preserves the original The Customer Factor prospect creation date as the HighLevel Contact date_added field, maintaining an accurate timeline for lead age and follow-up scheduling.

The Customer Factor stores a business name field on customer records. This migrates as a HighLevel Company record. If multiple The Customer Factor customers share the same business name, FlitStack creates one Company and links all associated Contacts via the Company-Contact relationship.

Estimates in The Customer Factor (with line items, pricing, and status) become HighLevel Opportunities. The estimate total maps to Opportunity monetary value. Estimate status (pending, approved, rejected) maps to pipeline stage values — approved estimates route to a Won stage; rejected or expired estimates route to Lost. Line items are preserved in a custom text field since HighLevel Opportunities do not natively store itemized line items.

HighLevel Pipelines are the deal-tracking equivalent of The Customer Factor's estimate status. FlitStack creates a Pipeline in HighLevel with stages matching the estimate statuses in use. Teams can rename stages (e.g., 'Pending', 'Approved', 'In Progress') to match their existing workflow before the migration runs.

Jobs in The Customer Factor (service appointments with date, crew, and work details) become HighLevel Tasks. The job date maps to Task due date; job notes map to Task description. A custom 'Work Order Number' field on the Task preserves the original The Customer Factor job identifier for traceability.

Invoices in The Customer Factor migrate as HighLevel Invoices with the same line items, totals, tax amounts, and payment status. Paid status maps to 'Paid' in HighLevel; outstanding invoices carry the balance forward. FlitStack maps the invoice date, due date, and any custom invoice formatting fields to their HighLevel equivalents.

Any custom fields configured on The Customer Factor customer record (e.g., service type, billing cycle, referral source) are recreated as custom fields in HighLevel on the Contact object. FlitStack creates the fields before migration and maps values during the import phase. Field type is preserved — text, number, date, and pick-list fields map to equivalent HighLevel field types.

Tags in The Customer Factor migrate as Tags in HighLevel. Tag names are preserved exactly. FlitStack handles tag normalization (trimming whitespace, deduplication) before import so the tag vocabulary is clean in HighLevel from day one. This normalization step is critical for reporting accuracy, as inconsistent tagging in the source system can otherwise fragment analytics and segmentation in HighLevel.

The Customer Factor's automated follow-up sequences (email drip campaigns, reminders, and callback triggers) do not have a structural equivalent in HighLevel and cannot be exported. FlitStack documents the sequence logic — trigger conditions, delay intervals, and message content — as a rebuild reference document. HighLevel's Workflows engine offers a more powerful replacement, and the reference document accelerates the rebuild.

Communication logs attached to The Customer Factor customer record migrate as HighLevel Activities (Log Call or Log Email) against the Contact. Original timestamps and any notes in the log body are preserved. HighLevel attaches activities to the Contact timeline automatically.

Free-text notes on The Customer Factor customer record migrate as Notes in HighLevel, attached to the Contact. The note body and creation timestamp transfer directly. Notes are not linked to Opportunities or Tasks unless they reference a specific job or estimate identifier.

The Customer Factor stores recurring service frequency (e.g., 'weekly', 'bi-weekly', 'monthly') on the customer record. This migrates as a custom pick-list field on the HighLevel Contact. Teams can then use HighLevel's Workflows to auto-generate Tasks on a recurring schedule using the frequency value as a trigger condition.

Custom rate or pricing agreements stored in The Customer Factor customer profile migrate as a custom currency field on the HighLevel Contact. If the rate applies per job, FlitStack also attaches it to the corresponding Opportunity for per-deal visibility. When a per-job rate exists, FlitStack creates a corresponding custom currency field on the Opportunity so sales teams can see client-specific pricing directly within the deal context without needing to open the Contact record.