Migrate from Less Paper Co. to Twenty CRM

Less Paper Co. customer records map directly to Twenty CRM People. The name, email, phone, and address fields translate field-for-field. A customer record that has multiple service locations maps to one People record with each location as a separate Company record linked via the companyId relation.

Less Paper Co. business accounts (property or facility addresses where service occurs) map to Twenty CRM Companies. Domain, industry, and address fields map directly. Companies with no corporate name default to the service address as the company name. Parent-child hierarchies in Less Paper Co. translate to Twenty's Parent Company relation.

Work orders have no native equivalent in Twenty CRM. We create a WorkOrder custom object in Twenty's Settings → Data Model before migration. Standard fields map: work order ID, title, description, status, priority, created date, and closed date. The customer link becomes a relation to People; the service location becomes a relation to Companies.

Each line item on a Less Paper Co. work order — labor hours, parts used, service codes — becomes a record in a WorkOrderLineItem custom object related to the parent WorkOrder. Line item types map to a custom pick-list field (labor, parts, misc). Unit price and quantity map to number fields for cost tracking.

Less Paper Co. technicians who also appear as customers (e.g., for internal work orders) merge into a single People record in Twenty with the role differentiated by a custom Role__c field. External technicians not yet in Twenty workspace are created as People records; owner resolution by email attaches them to the correct WorkOrder records.

Less Paper Co. scheduling entries — technician, date, time window, and location — map to Twenty CRM Tasks. The scheduled date becomes the due date; the time window maps to custom time fields (ScheduledStart__c, ScheduledEnd__c). Task status tracks completion against the original Less Paper Co. appointment status (scheduled, in-progress, completed, cancelled).

Less Paper Co. parts inventory — part number, name, stock quantity, reorder level, and vendor — migrates to an InventoryItem custom object in Twenty. Stock level maps to a number field; vendor maps to a Companies relation. Low-stock alerts become custom checkbox fields that can trigger Twenty workflow notifications post-migration.

Less Paper Co. payment records — amount, method, status (collected, pending, refunded) — migrate as custom fields on the WorkOrder custom object (PaymentAmount__c, PaymentMethod__c, PaymentStatus__c). Because Twenty CRM lacks a native payment module, we preserve the financial data as reference fields and document the rebuild path using Twenty's workflow builder and third-party payment integrations.

Less Paper Co. PDF documents attached to work orders and signature captures migrate as Twenty CRM Notes attached to the corresponding WorkOrder record. We download the original files and re-upload them to Twenty's attachment model, preserving the original upload timestamp and uploader name.

Less Paper Co. communication logs split into two records in Twenty: free-form notes about customer preferences or property conditions become Notes on the People record; action items (follow-up calls, scheduling changes) become Tasks with the appropriate assignee and due date. The original timestamp and author are preserved on both.