Migrate from Amwork to Twenty CRM

Amwork Contacts migrate to Twenty Person records. Name, email, phone, address, and lifecycle stage map to Twenty's standard Person fields. Custom contact fields attach as custom fields on the Person object via Twenty's field creation API. We resolve the Contact-to-Company link and create the corresponding Company record first so that the Person-Company relationship is established at insert time.

Amwork Company records map directly to Twenty Company. Company name, domain, industry, address, and linked contact count migrate as-is. The domain field populates Twenty's Website field, which supports CRM enrichment triggers if the Twenty enrichment extension is enabled. Companies are migrated before Persons to satisfy the Person.CompanyId lookup.

Amwork Deals migrate to Twenty Opportunity records. Deal name, value, stage, expected close date, owner, and associated Company and Contact links transfer directly. The Amwork pipeline stage name maps to Twenty's Opportunity Stage field. We create any missing stage values in Twenty before migration so that Deal stage assignments land without post-migration corrections.

Amwork Lead records (from the separate Deals and Leads section) migrate to Twenty Person records. Lead status maps to a custom picklist field on Person since Twenty does not have a separate Lead object. We preserve the original Amwork lead score, source, and status as custom fields on the Person record for segmentation and reporting after migration.

Amwork Projects are top-level workspace containers with no direct Twenty equivalent. We convert each Amwork Project into a set of Tasks in Twenty, linked to the associated Company or Person. Project name and description become a top-level Task or a custom field on the task set. Project members without existing Person records are provisioned as Person records first, then assigned as Task assignees.

Amwork Tasks migrate to Twenty Task records with assignees, due dates, priorities, and checklist sub-items preserved. Parent-child task hierarchies convert to Twenty's task threading model. Tasks that were time-tracked in Amwork carry a link to the corresponding time-entry Note or custom object record. Open and completed status maps directly to Twenty's Task status values.

Amwork time entries have no native equivalent in Twenty's data model. We preserve them as Notes attached to the associated Task, using a timestamped Note body that includes duration, description, and billable flag. Alternatively, if the customer requires billable-hour reporting, we create a custom TimeEntry object in Twenty with duration, date, description, and billable fields, and link it to the associated Task and Person via lookup fields.

Amwork custom fields (text, number, date, choice types) attach to Tasks via project-level activation. We map each custom field to a Twenty custom field on the equivalent object (Person, Company, Opportunity, or Task). Field types map to Twenty's supported types: text to TEXT, number to NUMBER, date to DATE, and choice to SELECT. Multi-select choices in Amwork map to Twenty's multi-select field.

Amwork user records (name, email, role, active status) map to Twenty User accounts. We match by email during migration. Any Amwork user without a matching Twenty User account enters a reconciliation queue for the customer's admin to provision before Person and Opportunity imports resume, since OwnerId references must resolve at insert time.

File attachments on Amwork Tasks and Deals migrate as URLs pointing to the original hosted file location, or as base64-encoded attachment records if the destination Twenty instance supports file storage. Large attachment batches (over 1,000 files) migrate in chunked batches to respect API throughput limits and avoid timeouts.