Migrate from Novo Work Order to Twenty CRM

Novo Work Orders map to Twenty Opportunities. The WO number becomes the Opportunity name or a reference field; work-order status (Open, In Progress, Completed, Closed) maps to a custom pick-list field on the Opportunity since Twenty does not have a native status enum. The original WO create date is preserved as a custom datetime field for audit continuity.

Novo requesters — the individuals who submitted or are associated with a work order — map directly to Twenty People records. Their name, email, phone, and address fields transfer as-is. A person may be linked to multiple work orders, which Twenty handles by linking the same Person record to multiple Opportunity records.

Novo customer accounts (the organization or property owning the asset) map to Twenty Companies. Company name, domain/website, industry, and address fields transfer directly. Multi-location customers with separate addresses per work order preserve each location address as a custom field on the Company or as a separate Company record per location.

Novo assets (equipment, vehicles, facilities) have no native equivalent in Twenty's standard object set. FlitStack creates a custom Asset object in Twenty via the /metadata API and maps asset name, asset ID, location, make/model, and condition fields. Each Asset links to the related Company and Opportunity records using relation fields.

Work order descriptions, internal notes, and resolution summaries map to Twenty Notes records. Each Note is linked to its parent Opportunity and Person records so the full work-order context surfaces in the Twenty timeline view. Original timestamps and note authors are preserved.

Novo file attachments on work orders (photos, PDFs, inspection reports) do not migrate via CSV import. FlitStack re-uploads each attachment to Twenty's file storage, linking the file to the corresponding Opportunity record. Inline images in notes are downloaded, re-hosted, and the links updated in the Note body.

Novo technicians and work-order assignees resolve by email match against Twenty Workspace Members. Unmatched users are flagged before migration — the team either invites them to Twenty first or assigns their records to a fallback Workspace Member. Technicians without Twenty accounts cannot be linked automatically.

Novo custom fields on work orders (e.g., service type, priority level, permit number, damage category) map to custom fields on the Twenty Opportunity object. Each custom field is created in Twenty's schema via the settings UI or API before migration validation runs. Field types (text, number, date, pick-list) are matched to Twenty's supported field types.

Novo preventive maintenance schedules and recurring work-order templates have no native equivalent in Twenty. These are documented as a rebuild reference export and can be recreated in Twenty using custom objects, date fields, and workflow triggers. FlitStack does not migrate the scheduling logic — it is a manual-rebuild item.

Novo work-order line items or service tasks (labor hours, parts used, service codes) typically map to a custom text area or JSON-formatted custom field on the Twenty Opportunity, since Twenty's standard Opportunity object does not have a native line-item sub-object. Complex multi-line structures may require a custom OpportunityLineItem object.