Migrate from Powered Now to Twenty CRM

Powered Now clients map to Twenty People records. The client name splits into firstName and lastName where available; single-field names land as a single lastName with firstName blank. Email, phone, and address fields map directly. Site address and billing address require field splitting — see field_mapping for detail.

If the Powered Now client is a business entity (rather than an individual homeowner), it also maps to a Twenty Company record. The client's trading name or company name becomes the Company name. FlitStack creates both Person and Company records and links them via companyId on the Person side.

Powered Now jobs map to Twenty Opportunities. The job name becomes Opportunity name. Job status (Unscheduled, Scheduled, In Progress, Completed, Invoiced, Paid) migrates as a custom pick-list field (Job_Status__c) since Twenty has no native job object. Close date maps to the opportunity closeDate; the close date is set to the scheduled completion date or remains open-ended for unscheduled jobs.

Powered Now quotes map to Twenty Opportunities with a Quote_Number__c custom field and line-item details stored in custom fields (Quote_Line_Items__c as long-text or via a custom Quote_Line_Item__c custom object). If quotes need to remain standalone records, FlitStack creates a custom Quote object in Twenty before migration.

Powered Now invoices map to Opportunities with invoice number, total amount, balance due, and payment status stored in custom fields. Teams that need full invoice history as records create a custom Invoice object in Twenty before migration — FlitStack maps invoice line items to that object.

Powered Now purchase orders have no Twenty native equivalent, so FlitStack creates a custom Purchase_Order__c object before migration with fields for PO number, supplier, total cost, status, and a lookup to the related Opportunity via opportunityId. Supplier invoices map to a linked custom Supplier_Invoice__c object that records invoice number, supplier reference, amount, and payment status, enabling cost tracking against each job.

Powered Now diary entries (scheduled time slots for jobs) map to Twenty Tasks linked to the corresponding Opportunity. The task dueDate is the diary slot start time. All-day diary entries with no specific time become Tasks; entries with explicit start and end times become Events.

Powered Now certificates (gas safety certificates, electrical certificates) attach to jobs. These migrate as Twenty Notes linked to the Opportunity (job) record, with the certificate type and expiry date stored in custom fields on the Note or as a custom Certificate__c object.

Powered Now custom fields on clients (e.g., trade licence number, insurance policy reference) map to custom fields on the Twenty Person object. All custom fields must be created in Twenty Settings → Data Model before the CSV import step runs.

Powered Now custom fields on jobs map to custom fields on the Twenty Opportunity object. Examples include site access instructions, required materials, or engineer notes. Each custom field is created in Twenty before migration; transformation logic handles pick-list value mapping for select-type fields.

Powered Now team members (engineers, office staff) map to Twenty Workspace Members. Owner assignment on jobs and quotes resolves by matching the Powered Now email address to a Twenty user account; FlitStack generates a pre‑migration mapping report showing matched and unmatched emails. For any unmatched owners, the admin must either invite the user to Twenty or reassign the record to a fallback owner before the import runs.

Powered Now file attachments on jobs, quotes, and invoices are downloaded and re‑uploaded to Twenty's file storage, where each file is linked to its parent record (Opportunity, Person, or custom object) using the recordId. FlitStack uses Twenty's REST API to upload files, preserving the original filename. If a file exceeds Twenty's size limit, it is flagged for manual handling; otherwise the attachment appears in the record's Files section.

Powered Now automated certificate reminders, job routing triggers, and form-based automations do not have a native equivalent in Twenty. These must be rebuilt manually in Twenty's workflow builder (Settings → Workflows) or via an external automation platform. FlitStack exports the Powered Now workflow definitions as a reference document for the rebuild.

Powered Now supplier invoices link to purchase orders and track costs against jobs. These map to a custom Supplier_Invoice__c object created in Twenty, with fields for invoice number, supplier reference, amount, and linked opportunityId for cost tracking against the job.