Migrate from Corteza CRM to Freshsales

Corteza Lead records map to Freshsales Lead with standard fields (first name, last name, email, phone, rating, status) migrated directly. Corteza's lead conversion workflow creates Accounts, Contacts, and Opportunities on conversion; Freshsales converts Leads into Accounts, Contacts, and Deals with configurable field mapping via Admin Settings > Leads > Field mapping. We preserve the original Corteza lead status and any custom lead fields as Freshsales custom fields. Note: during classic Freshsales account migration, Leads with duplicate email addresses are automatically merged; we flag this behavior and run deduplication before migration to prevent unintended record collapse.

Corteza Account records map to Freshsales Account with company name, industry, address, and social media fields migrated directly. The account name becomes the Freshsales Account Name and serves as the dedupe key. If Corteza stores a website domain on the Account, it migrates to the Freshsales Website field. We preserve the account-industry classification for segmentation.

Corteza Contact records map to Freshsales Contact with first name, last name, email, phone, and job title migrated directly. The contact-account relationship (parent Account link) is resolved by matching the Corteza Account Name or Account ID to the Freshsales Account record created earlier in the migration sequence. We validate that every Contact has a resolved AccountId before insert to avoid orphaned contacts.

Corteza Opportunity records map to Freshsales Deal with stage, amount, probability, and close date migrated directly. The Corteza opportunity.accountID maps to the Freshsales AccountId lookup, and opportunity.ownerID resolves via email match to the Freshsales User. Deal stage values are mapped to Freshsales Deal stage values configured in Admin Settings. Probability and close date migrate as custom fields if the customer's reporting depends on them.

Corteza Campaign records map to Freshsales Campaign with campaign name, type, status, and start/end dates. CampaignMember records linking Contacts and Leads to the Campaign migrate as Freshsales Campaign Members with Status (responded, sent, opted out). Activity history on campaigns (sent emails, opened tracking events) does not migrate as Freshsales campaign reporting is built from Freshsales' own email tracking rather than historical imports.

Corteza Case records map to Freshsales Case with status, priority, origin, and resolution fields. Case-account and case-contact relationships are preserved by resolving the Account and Contact lookups at migration time. If the destination Freshsales account is on the Growth plan without a dedicated Service Cloud license, Cases may be handled as custom Deal or Task records; we confirm the plan tier during scoping.

Corteza Task records migrate to Freshsales Task with status, due date, subject, description, and assignee preserved. Assignee resolution is by email match to Freshsales User. Tasks related to Leads, Accounts, Contacts, or Deals carry the corresponding WhatId or WhoId lookup. Standalone tasks without a parent record migrate with no lookup reference.

Corteza Event records (meetings, calls) migrate to Freshsales Task with TaskSubtype or custom event type field capturing the activity type. Start datetime, duration, and location migrate as custom fields on the Task. Attendee references are stored as a text field listing the resolved Contact or Lead names because Freshsales Tasks do not have an EventRelation equivalent for attendee tracking.

Corteza's low-code module builder can produce entirely custom modules with non-standard field types and validation rules. We pre-create the corresponding custom fields in Freshsales under the appropriate standard object (Lead, Contact, Account, or Deal) during the schema design phase. Custom modules that require standalone object behavior require Freshsales Enterprise ($69/user/mo) for custom objects; we confirm the destination plan tier and advise on upgrade if needed before migration begins.

Corteza Product records with pricing information stored in PricebookEntry migrate to Freshsales Product. Product name, SKU, and unit price migrate directly. If the customer uses quote generation, we migrate the product catalog and price list so that Deals can reference products at migration time.