Migrate from Amwork to Freshsales

Amwork Contact records migrate directly to Freshsales Contact. We map Amwork fields (name, email, phone, address, lifecycle stage, owner assignment) to Freshsales Contact fields. Any Amwork custom contact fields are pre-created as Freshsales custom fields before migration so values land in typed fields rather than generic notes. Owner resolution is by email match against Freshsales User records; unmatched owners go to a reconciliation queue for admin provisioning before Contact insert.

Amwork Company records map to Freshsales Account. Company name becomes Account Name, domain becomes Website, and linked contact relationships are preserved through a contact-account lookup that we resolve at migration time. Account is inserted before Contact so the AccountId lookup relationship is satisfied at the moment of Contact insert. Industry and address fields map directly where present in the Amwork export.

Amwork Deals migrate to Freshsales Deals with deal value, stage name, owner, and linked contact and company lookups preserved. We resolve Amwork's pipeline stage names against Freshsales' stage configuration, creating any missing stages in Freshsales before import so that stage assignment is resolved at insert time rather than requiring a post-migration correction step.

Amwork Lead records migrate to Freshsales Lead with their status field mapped to Freshsales lead_status. Amwork's lifecycle_stage property on leads is preserved in a custom field on the Freshsales Lead for reporting continuity. Leads in Freshsales can be converted to Contact and Account with a single action, which is the recommended post-migration step for active lead records.

Amwork Tasks migrate to Freshsales Task records. We preserve parent-child task hierarchies where present, assignees map to Freshsales User records by email, and due dates and priorities transfer directly. Tasks that were billable or had time entries associated with them are flagged so that the corresponding time entries can be linked to the Freshsales Task or the parent Contact.

Amwork time entries log hours against Tasks and Projects, not directly against Contacts or Companies. We migrate time entries as Freshsales Task records with the original duration, date, description, and billable flag preserved. The associated Task from Amwork maps to the corresponding Freshsales Task, and the linked contact or company is set as the WhatId on the Freshsales Task for activity timeline continuity. This routing resolves the structural mismatch between Amwork's task-attached time model and Freshsales' contact-centric activity model.

Amwork custom fields on contacts, companies, and deals are pre-created in Freshsales before any record migration begins. We map Amwork field types (text, number, date, choice) to equivalent Freshsales field types. Choice-type fields from Amwork become Freshsales picklist fields with the same option values. The field API name in Amwork is used as a reference when naming the Freshsales custom field to preserve traceability between the two systems.

Amwork Users and Owners referenced on Contacts, Companies, Deals, and Tasks are mapped to Freshsales User records by email match. We extract every distinct owner_id from the Amwork export and cross-reference against the Freshsales User table. Any owner without a matching Freshsales User is held in the reconciliation queue and the customer's Freshsales admin provisions the User before record migration resumes. Active and inactive status is preserved where available in the Amwork export.

Amwork deal pipelines with user-defined stages map to Freshsales Deal stages. We create any Amwork pipeline stages that do not exist in Freshsales as new stage values before deal migration, and we map Amwork stage probabilities to Freshsales stage weights. If multiple Amwork pipelines exist, each maps to a separate Freshsales pipeline view, which the admin configures in Freshsales Settings.

File attachments on Amwork Tasks and Deals migrate as Freshsales File records linked to the parent record. Large attachment batches are chunked and rate-limited to stay within Freshsales API throughput. File metadata (original filename, upload date, file size) is preserved and attached to the corresponding Freshsales record on insert.