Migrate from Convert Wire to Freshsales

Convert Wire Contact maps directly to Freshsales Contact. Freshsales requires an AccountId lookup for every contact — contacts without a primary company association land under a default Account or your specified fallback Account. Email uniqueness is validated against existing Freshsales contacts before insert to prevent duplicates and maintain data integrity across the migration.

Convert Wire contacts in a 'Lead' lifecycle stage route to Freshsales Lead. Contacts flagged as 'Customer' or 'Active' route to Freshsales Contact. The split is based on Convert Wire's lifecycle stage field value — each distinct stage value maps to a corresponding Freshsales lead status or lifecycle stage pick-list entry.

Convert Wire Company maps to Freshsales Account. Parent-company hierarchies in Convert Wire map to Freshsales Parent Account field — the parent must migrate first so foreign keys resolve. Multi-company associations on a single contact collapse to the most-recently-modified as the primary AccountId.

Convert Wire Deal maps to Freshsales Deal (the Freshsales UI label; API object is Opportunity). Pipeline stages map via value_mapping — each Convert Wire stage name maps to the corresponding Freshsales stage name in your target pipeline. Probability percentages are preserved as a custom field for reporting continuity.

Convert Wire pipelines with multiple stages per deal become Freshsales Deal Pipelines. Freshsales supports multiple pipelines per account — each Convert Wire pipeline becomes a separate Freshsales pipeline. Stage order, names, and probability percentages are mapped value-by-value during migration plan setup, ensuring each pipeline's workflow stages translate accurately to Freshsales.

Convert Wire tasks migrate as Freshsales Sales Activities. Task subject, due date, status, and priority transfer directly. Owner email resolves to the Freshsales user by email match — unmatched owners are flagged before migration commits so you can assign a fallback owner.

Convert Wire notes migrate as Freshsales Notes with rich-text formatting preserved. Notes attached to a specific record carry the parent object reference in Freshsales so they appear in the record's timeline view, maintaining context and conversation history across migrated records.

Convert Wire custom fields on any object require Freshsales custom field creation before migration. FlitStack delivers a custom field creation plan — field type, pick-list values, and required/unique flags are set per Freshsales' allowed types. Custom fields on Convert Wire's Lead object need Freshsales lead field mapping configured in the Leads module settings.

Convert Wire file attachments on contacts, companies, or deals re-upload to Freshsales Files. File size limits apply per Freshsales storage tier — files exceeding the limit are flagged and reported before the migration runs. Inline images in notes are downloaded and rehosted as Freshsales file attachments.

Convert Wire owner records resolve by email match against Freshsales user accounts. Active Freshsales users with matching email receive their assigned records automatically. Owners with no Freshsales match are held in a staging queue — FlitStack flags these before migration so your admin can either invite the user or reassign records to a designated fallback owner.