Migrate from ConSol to Freshsales

ConSol contacts map directly to Freshsales Contacts. Email, phone, job title, and address fields carry across without transformation. If a ConSol contact has no associated company, it lands in Freshsales as a standalone Contact. Owner is resolved by email match to Freshsales users.

ConSol companies map to Freshsales Accounts using the same name and address fields. Industry and employee-count fields migrate as direct text or pick-list values where ConSol provides them. Multi-location ConSol companies can be represented as a primary Account with child Account records if the destination schema supports it.

ConSol tickets and incidents translate into Freshsales Deals. Ticket priority (Low, Medium, High, Critical) maps to a custom Deal Priority field since Freshsales has no native ticket-priority equivalent. The original ConSol ticket number is stored as a custom reference field on the Deal for traceability.

ConSol ticket status values (Open, In Progress, Pending, Resolved, Closed) map to Freshsales Deal stage values. The mapping plan specifies which ConSol status maps to which Freshsales pipeline stage per pipeline. Closed tickets can route to a 'Closed Won' or 'Closed Lost' stage based on your specified rule.

ConSol service requests that represent billable or trackable work items become Freshsales Deals with a custom 'Request Type' field set to 'Service Request'. This preserves the operational distinction while fitting the deal model Freshsales uses for pipeline management. If your ConSol service request includes custom fields such as billing code or service level agreement, those fields are also migrated as custom Deal fields in Freshsales, preserving data completeness.

ConSol projects have no native Freshsales equivalent. We discuss with you whether to map projects to Freshsales Deals (using a custom 'Project' pick-list value), or to a Freshsales custom module (Enterprise plan only) for richer project-level fields like milestones, budget, and timeline.

ConSol assets tied to specific accounts map as linked records. In Freshsales Enterprise, a custom 'Asset' module can be created. In Growth/Pro, asset data attaches to the related Account as custom fields, with asset name, serial number, and status preserved.

ConSol engagement records (emails, calls, meetings) map to Freshsales Sales Activities. Original timestamps and owner assignments are preserved. Call duration, outcome, and meeting participants carry across as activity-specific fields where ConSol captures them. For calls, the call duration is stored in minutes, and the outcome field captures the result (e.g., Connected, Voicemail). Meeting participants list includes invitees and their response status where available.

ConSol notes migrate as Freshsales Notes attached to the parent record (Contact, Account, or Deal). Rich-text formatting is preserved where ConSol stores it. Notes without a parent record are attached to the most relevant related entity based on contact or company linkage.

ConSol custom objects and their fields map to Freshsales custom objects (Enterprise) or custom fields on native objects (Growth/Pro). We deliver a custom-object migration plan that specifies which custom object becomes a Freshsales custom module and which fields attach as custom properties to Deals, Contacts, or Accounts.

ConSol users are matched to Freshsales users by email address. Active ConSol users who do not yet have Freshsales accounts are flagged before migration. You either invite them to Freshsales first or reassign their records to an existing Freshsales user during the migration run.

ConSol file attachments on tickets, contacts, or companies are re-uploaded to Freshsales Files and linked to the corresponding record. Freshsales file size limits (default 25MB per file) apply. Inline images in rich-text notes are extracted and rehosted as Freshsales file attachments.