Migrate from WORKetc to Twenty CRM

WORKetc Contact records map directly to Twenty Person records. Standard fields (name, email, phone, address, lifecycle information) map to the corresponding Twenty Person fields. We preserve the WORKetc lifecycle stage or status as a custom text field on the Person record for audit. Owner assignment in WORKetc (the assigned user) maps to the Twenty Person's workspaceMemberId via email-based lookup resolution.

WORKetc Company records map to Twenty Company. The company domain becomes the Company Website field and is used as the dedupe key during CSV import. Company is imported before Person so that the Person can reference a valid CompanyId via lookup. Company-level custom fields map to custom fields on the Twenty Company object created in Settings Data Model before import.

WORKetc Lead records capture early-stage prospects through to conversion. We map these to Twenty Person records, preserving the lead status, source, and conversion flag as custom fields. If the lead has been converted to a Contact in WORKetc, we ensure the corresponding Person record in Twenty reflects the converted state and maintains the original lead creation date.

WORKetc Deals link to Companies and Contacts with stage, amount, and probability. We map Deals to Twenty Opportunity records, preserving deal amount, stage name, probability (if present), and close date. The Opportunity is linked to the corresponding Company and Person records resolved from the WORKetc deal associations. Pipeline stages are recreated in Twenty's pipeline configuration before import.

WORKetc Projects with Types and Stages carry weighted progress percentages per stage that do not map to standard project management tools. We export the full stage configuration (stage names, custom percentage weights, stage order) and map project progress to a duration-based calculation using the stage weights as a proxy. If the customer uses a simple task-completion ratio (before Types and Stages was enabled), we map directly. Projects become a Twenty Custom Object with related Task records representing milestones.

WORKetc Tickets (Support Cases) link to Customers, Companies, and Projects with status, priority, and conversation threads. We export ticket records with full conversation history and map them to a Twenty Custom Object for support cases. Conversation threads are stored as Note records linked to the ticket record. Status and priority become custom select fields. If Twenty's native Task object is preferred, tickets can map there with status mapped to Task status values.

WORKetc Invoice records include line items, totals, and payment status linked to Customers and Projects. We export invoice headers and line items as a Twenty Custom Object. Payment history and linked bank transaction records require separate reconciliation and do not typically migrate. The invoice PDF references (file URLs) migrate as text fields; actual PDF binary export depends on the customer's document storage configuration.

WORKetc Custom Field definitions and values are exported for all objects. Custom field types (dropdown, text, date, number, checkbox) require mapping to equivalent Twenty field types. We pre-create all custom fields in Twenty's Settings Data Model before data import begins. Fields must exist before import because the CSV import creates records, not fields. The customer reviews custom field necessity during scoping; we recommend leaving behind unused custom fields per Twenty's migration guide recommendation.

WORKetc User records (name, email, role, permission level) map to Twenty Workspace Members. We resolve by email match. The customer's admin must invite all team members in Twenty Settings Members before migration begins because OwnerId and assignee references on records require existing workspace members. Roles and permission levels from WORKetc are mapped to Twenty workspace role definitions.

WORKetc Contractor Portal users are a separate identity class with limited access and may lack standard email addresses or user credentials. We map contractor records to Twenty Person records with a custom boolean or text property (e.g., is_contractor__c or contractor_type__c) set to true. These records do not become Workspace Members because Twenty has no contractor portal concept. The customer defines the contractor property name during scoping.

WORKetc file management stores documents linked to records. We export file metadata (name, type, size, URL reference, linked object, linked record ID). Actual file binary export depends on whether WORKetc exposes file download endpoints via SOAP API and whether Twenty's document storage is configured. We flag file export feasibility during scoping and migrate metadata with URL references as a fallback.

WORKetc KB articles and categories are stored separately from CRM records. We export article content, title, category assignments, and author information. Rich formatting and embedded media may require post-migration review. Articles become a Twenty Custom Object with category stored as a custom select field. If Twenty introduces native Knowledge Base support, reclassification is straightforward at that point.

WORKetc workflow rules and automation triggers are not exposed via API. These must be reconstructed manually in Twenty using the exported workflow descriptions as reference. We deliver a written inventory of every active WORKetc workflow with its trigger conditions, actions, and recommended Twenty equivalent. The customer's admin rebuilds them in Twenty's settings UI.