Migrate from Kordeva to Freshsales

Kordeva Contact records map 1:1 to Freshsales Contact. Standard fields (name, email, phone, address) transfer directly. Custom attributes retrieved via Kordeva's Custom Fields API migrate to Freshsales custom fields created in Admin Settings under the Contacts module. We enumerate all custom field definitions during discovery and create matching Freshsales fields before import. Email serves as the dedupe key; duplicates are flagged for customer review before insert.

Kordeva Company records map to Freshsales Account. The company-contact association is preserved during migration by resolving the Contact's account_id at insert time. If Kordeva stores domain or industry as custom fields, we map those to Freshsales Account Website and Industry picklist values. Account is created before Contact import to satisfy the lookup dependency.

Kordeva Deals map to Freshsales Deals with the pipeline stage name preserved in the deal stage field. Stage configuration (stage-to-stage mapping and probability) requires customer review because pipeline layouts differ between systems. We map Kordeva stage names to Freshsales deal stages during scoping, and the customer confirms the stage sequence before production migration. Deal amount, close date, and owner migrate directly.

Kordeva activity records (calls, emails, meetings, tasks) logged against Contacts and Deals migrate to Freshsales Tasks and Events. Call records become Tasks with TaskSubtype set to Call and call duration preserved. Meeting records become Events with start and end times and attendee data. Email records become Tasks with a custom field holding the email body for display in the activity timeline. We link each activity to the parent Contact or Deal via the WhoId and WhatId fields resolved at migration time.

Kordeva's Custom Fields API exposes extended resource attributes that we enumerate during discovery. We create equivalent custom fields in Freshsales under the appropriate module (Contacts, Accounts, Deals) before migration. Field types are mapped: text to text, number to number, date to date, picklist to picklist. If Kordeva uses a field type not supported by Freshsales (e.g., a complex multi-level lookup), we flag it during scoping and propose an alternative representation.

Kordeva's Regular tier includes Accounts and Invoicing as a bundled feature. Invoice records, line items, and payment status migrate to Freshsales Account with custom fields carrying the invoice data, since Freshsales does not have a native invoicing object at the CRM tier. We perform field-level mapping for invoice schema differences and flag any unsupported invoice attributes (e.g., tax rate structures, partial payment schedules) for customer review.

Kordeva's Intelligent Workflow feature is gated at the Premium tier. We confirm the customer's tier during scoping. If Premium features exist, we inventory every active workflow (trigger, conditions, actions) and deliver a written mapping document with recommended Freshsales Workflow equivalents. Workflows do not migrate as code; the customer or a Freshsales partner rebuilds them post-migration. This applies only to teams on the Premium tier.

Kordeva Owners referenced on Contact, Company, Deal, and Activity records map to Freshsales User by email match. We extract every distinct owner ID, query the corresponding email, and resolve against the Freshsales User table. Any Owner without a matching User goes to a reconciliation queue for the customer's admin to provision before record import resumes.