Migrate from WORKetc to Freshsales

WORKetc Contact records map directly to Freshsales Contact. Standard fields (name, email, phone, address, lifecycle information) map to Freshsales native contact fields. Owner assignment resolves by matching WORKetc owner email to a Freshsales User. WORKetc custom contact fields must be pre-created in Freshsales as typed fields (text, number, date, dropdown) before migration so values are not silently dropped during CSV import.

WORKetc Company records map to Freshsales Account. The Company → Contact relationship is preserved by importing Accounts first, resolving the Freshsales Account ID, then linking each Contact to the parent Account during Contact import. Company-level custom fields map to Freshsales Account custom fields with pre-creation required.

WORKetc Lead records map to Freshsales Lead. Lead status, source, and converted-flagged records transfer directly. During Lead-to-Contact conversion in Freshsales, any custom Lead fields require explicit field mapping under Admin Settings → Leads → Add Field → Field Mapping to prevent data loss. We document this mapping in the pre-migration setup checklist and verify it before running the final import.

WORKetc Deals map to Freshsales Deal with stage, amount, probability, and close date preserved. WORKetc pipeline assignments map to Freshsales Deal Status values that we configure before migration. Closed-won and closed-lost reasons from WORKetc custom fields migrate to Freshsales deal custom fields.

WORKetc Projects use Project Types and Stages with custom percentage weights that have no Freshsales equivalent since Freshsales has no native project management object. We export full project records, stage configurations, milestone hierarchies, and task structures as a structured JSON export and deliver a written project migration guide recommending Freshsales Deal milestones, Tasks, or a third-party project integration (Asana, Trello) as the rebuild path.

WORKetc Invoices (headers, line items, totals, payment status linked to Customers and Projects) have no direct Freshsales billing equivalent. Freshsales does not include invoice generation or payment tracking. We export invoice metadata and line items as a CSV for the customer's accounting team to import into their billing tool or reconstruct as Freshsales Deal records with custom invoice fields. Payment history and linked bank transactions require separate export and are not in scope for standard CRM migration.

WORKetc full User records map to Freshsales User records by email match. Contractor Portal users are a separate identity class in WORKetc — they may lack standard email addresses or user credentials. Since Freshsales has no contractor portal concept, we map contractor users to Freshsales Contact records with a custom field Contractor__c set to true. Owner assignment for contractor-linked CRM records resolves against the managing User rather than the contractor record.

WORKetc Tickets (linked to Customers, Companies, and Projects with status, priority, and conversation threads) have no direct Freshsales equivalent object. Freshsales Conversation Management supports ticket-like workflows for customer communication but is scoped to chat and email threads. We export ticket records with conversation history and map open ticket status to Freshsales custom fields on Contact or Deal. Full ticket-to-case migration requires Service Cloud or a Freshdesk integration, which is a separate scope decision.

WORKetc custom field definitions and values export per object (Contact, Company, Lead, Deal). Each custom field requires pre-creation in Freshsales under Admin Settings with matching field type (dropdown, text, date, number) before the migration CSV is loaded. Dropdown-type WORKetc fields require Freshsales picklist value options to be created first to avoid import rejection. We sequence custom field creation as a pre-migration step in the scope document.

WORKetc Knowledge Base articles and categories are stored separately from CRM records and have no direct Freshsales equivalent. We export article content, category assignments, and rich formatting as an HTML and JSON package. Post-migration, the customer's admin can recreate KB content in Freshsales Article Storage or in a connected Freshdesk instance. Embedded media and formatting may require manual review and repair.