Migrate from Customer Database App to Freshsales

Customer Database App stores every field on a flat contact record with no Account or Company concept. Freshsales separates contacts from accounts. We ask the customer whether each contact should be treated as a standalone Freshsales Contact with no Account (suitable for individual customers, freelancers, or B2C use) or whether we should derive a minimal Account from any company-name field present in the CSV. Email is used as the dedupe key for Contact import into Freshsales.

Every contact in Customer Database App supports unlimited user-defined fields with no enforced schema. We infer the active field list from the exported CSV column headers during discovery. Each column maps to a Freshsales custom field of the nearest matching type: text fields to Freshsales Text type, numeric values to Number type, dates to Date type, and comma-delimited multi-value fields to Multi-select Picklist. Fields with free-text values containing commas are quoted during CSV parsing to prevent delimiter collision.

Customer Database App uses a single Kanban-style pipeline with user-defined stage names stored as a label-value property on each contact record. We extract the distinct stage names from the exported CSV and configure matching deal stages in Freshsales. If the customer has deal-associated contacts (i.e., pipeline data attached to contacts), we create Freshsales Deals and link them to the corresponding Contacts after contact import completes.

Customer Database App stores customer groups and tags as comma-separated label strings on each contact record. We split these strings into individual tag values and create Freshsales Tag records. Tags are assigned to the migrated Contact via the tag_ids field. Any tag value that does not already exist in Freshsales is created during the import phase. Tag splitting preserves all original labels; no tag data is discarded.

Birthday is stored as a date field on the contact record in Customer Database App. Freshsales does not ship a dedicated birthday or anniversary field as standard. We map the birthday date to a Freshsales custom field of type Date with a label such as Birthday. If the customer prefers, it can also map to a custom Date field on the Contact record with any preferred naming convention chosen during scoping.

Vouchers are an app-specific object with no equivalent in Freshsales. The voucher balance is not exported via CSV from Customer Database App. We document this limitation in the migration scope and provide the customer with a supplemental CSV export of any voucher data available within the app for manual entry into Freshsales as a custom field value or external spreadsheet if needed.

The caller-ID log and call history are transient device-level records that are not included in the CSV or VCF export from Customer Database App. Freshsales has native phone and call logging capabilities; the customer can re-establish call logging within Freshsales post-migration. We document this gap in the scope and recommend that the customer capture current call-handling procedures as a separate operational reference document.

Contact images and PDF exports of individual records can be bundled into a ZIP archive alongside the CSV export from Customer Database App. We attach each contact's image or PDF to the corresponding Freshsales Contact record via the native file attachment mechanism. If the ZIP archive is not available, we flag this during discovery and the customer can regenerate the archive before migration begins.