Migrate from Contlo to Freshsales

Contlo Contacts with no purchase history or engagement score below a threshold map to Freshsales Lead. Contacts with purchase history, active deal associations, or high engagement scores map to Freshsales Contact attached to an Account. We compute the split during scoping using Contlo's contact properties (purchase_total, lifecycle_stage, segment tags) and preserve the original segment membership in a custom tag field for audit. Freshsales' lead conversion process creates an Account and Contact from the Lead when the record is qualified.

Contlo Segments are behavioral groupings used to target automations. We preserve segment membership as tags on each migrated Lead or Contact record using Freshsales' native tag feature. Segment rules (AND/OR logic, filter conditions) are documented as a written segment inventory for the customer's admin to recreate using Freshsales' filter views and dynamic lists. Segment rules do not translate to Freshsales automation triggers because the behavioral trigger model differs between platforms.

Contlo campaign templates migrate to Freshsales Email Templates with subject, body content, and sender settings preserved. Campaign metadata (send date, audience size, campaign type) migrates as a Freshsales Campaign record with the audience populated from the migrated Contacts matching the original segment criteria. Delivery logs and open/click event counts from Contlo are stored as a CSV export linked to the Freshsales Campaign for historical reference.

Contlo custom fields on Contacts and Segments map to Freshsales custom fields. We use Freshsales' custom field API to provision equivalent fields before migration, matching field types (text, number, date, dropdown) to Freshsales field types. Multi-select properties map to Freshsales multi-select picklists. Custom field data migrates directly if a Freshsales equivalent exists, or is stored as a JSON blob in a notes field if no direct type mapping is available.

Contlo event-level data (opens, clicks, conversions, engagement timestamps) is exported as a time-series dataset and linked to migrated Contact records via a custom engagement_history__c field. For high-volume event history (over 50,000 records), we create a custom object (EngagementEvent__c) with lookup to Contact to preserve the full timeline without exceeding Freshsales standard object storage limits. This data supports historical reporting in Freshsales analytics.

Contlo's brand-owned generative AI Model is a platform-specific artifact built from brand content and training data. It cannot be exported or transferred to Freshsales. We document the model configuration parameters (training data sources, content rules, AI Agent logic) in a written handoff document with recommended Freshsales AI equivalents (Freshsales Freddy AI for deal scoring and insights). The customer must re-train or re-create the AI model from scratch in Freshsales or a third-party AI tool.

Contlo automation flows are extracted as structured JSON with trigger types, conditions, delay actions, and branching logic. We deliver a written automation inventory document that lists each active flow with its trigger, conditions, and action steps. Freshsales Workflow rules handle automation differently (record-triggered, field-update, task-creation), so each Contlo automation requires a manual rebuild. The inventory document maps each Contlo flow to a recommended Freshsales Workflow configuration for the customer's admin to implement.

Contlo Voice Agents are AI-driven phone agents built from Contlo's library with routing logic and voice settings. We extract the agent configuration (intent mappings, response templates, routing rules) as structured data. Freshsales' built-in Caller functionality and Freshchat integration can replace some voice capabilities, but the AI-driven conversational model requires a separate rebuild. We document the Voice Agent setup as a rebuild guide and flag any Freshsales add-ons (Freshdesk Freshcaller, Freshchat) needed for equivalent functionality.