Migrate from Constructor to Freshsales

Constructor contacts map directly to Freshsales contacts. Email serves as the unique identifier for deduplication, so duplicate emails are merged or flagged. All standard contact properties—first name, last name, email, phone, job title, and address—migrate as direct field mappings. Custom fields on contacts are listed in pre‑migration plan and created in Freshsales before the run. Created and updated timestamps are preserved for audit continuity.

Constructor leads map to Freshsales leads. Lead status in Constructor maps to Freshsales lead status using a value-by-value mapping. Unconverted leads land in Freshsales as Lead records; leads that already converted in Constructor migrate as Contacts with a conversion flag preserved.

Constructor companies map to Freshsales accounts. Company name, domain (mapped to the website field), industry, employee count, and annual revenue migrate as direct fields. Constructor parent‑company hierarchies become Freshsales Parent Account lookups, requiring the parent account to be migrated first to resolve foreign keys. Custom fields on companies are listed in pre‑migration plan and created in Freshsales before migration. Created and updated timestamps are preserved for audit continuity.

Constructor deals migrate to Freshsales deals. Deal name, value, close date, owner, and stage migrate as direct or value‑mapped fields. Constructor deal pipelines map to Freshsales deal pipelines 1:1 basis, with stage names aligned per pipeline. Custom fields on deals are listed in pre‑migration plan and created in Freshsales before migration. Created and updated timestamps are preserved for audit continuity. Deal‑task links become Freshsales Task records linked to parent deal.

Each Constructor pipeline becomes a Freshsales deal pipeline. Stage names and probabilities are mapped value‑by‑value, preserving the original ordering of stages within the pipeline. Constructor pipelines that use non‑standard stage labels require custom stage creation in Freshsales before the migration runs; we provide a stage‑creation worksheet listing each required stage and its probability. After the pipeline is configured, deals migrate using the mapped stages.

Constructor lifecycle stage labels have no direct Freshsales equivalent. We create a custom pick-list field (Lifecycle_Stage__c) on the Contact and Lead objects in Freshsales and migrate Constructor stage values as pick-list options. Stages that don't match Freshsales' seven-stage model are preserved as-is in the custom field.

Constructor tasks that represent sales activities (follow-up calls, proposal reviews, meeting prep) map to Freshsales tasks. Original timestamps, owners, and task subjects are preserved. The Freshsales API creates each migrated task as a standalone Task record linked to the parent deal.

Constructor tasks that represent deliverables or milestones (e.g., signed contract, permit received) may not fit Freshsales' activity model. These split: simple yes/no milestones become custom checkbox fields on the Freshsales Deal; richer task data migrates as a custom text field for audit reference. Your team decides the split policy before migration runs.

Constructor notes migrate to Freshsales notes. Original created and updated timestamps, owner, and note body text are preserved. Rich‑text formatting such as bold, italic, and bullet lists is retained where the source format is compatible with Freshsales' note editor. If a note is linked to a deal or contact in Constructor, the migrated note maintains the same association in Freshsales via the appropriate lookup field.

Files attached to Constructor records—deals, contacts, companies—are downloaded and re‑uploaded to Freshsales Files, preserving the original file name and size. Freshsales enforces a 25 MB per‑file limit on Growth and Pro plans; files exceeding this threshold are split or linked. Inline images embedded in notes are extracted, re‑hosted as separate file records, and note is updated with new image URLs. Duplicate file names are handled via versioning to avoid data loss.

Constructor owner IDs are resolved by email match against Freshsales users. Owners with no matching Freshsales user are flagged before migration; your team either creates the Freshsales user first or assigns records to a fallback owner. No record lands without a valid Freshsales owner.

Constructor custom fields (on contacts, companies, deals) migrate to Freshsales custom fields of the corresponding type. Freshsales custom fields must be created before the migration runs; we deliver a custom field creation plan with correct Freshsales field types (text, number, pick-list, date, checkbox, etc.).