Migrate from Powered Now to Pipedrive

Powered Now clients map directly to Pipedrive People. Client name maps to Person name; primary contact details (email, phone) map to corresponding Pipedrive fields. If a client has multiple contacts, each contact migrates as a separate Person record, both linked to the same Organisation if a company record exists.

Individual contacts within a Powered Now client record migrate as separate Pipedrive People. Each person receives an email, phone, and address from the source contact record. If the same person appears across multiple clients, FlitStack AI flags duplicates before migration and applies a merge or link rule per your specification.

Powered Now companies map to Pipedrive Organisations. Company name, domain, industry, and employee count translate to Organisation name, address fields, and custom fields. If Powered Now stores a company without a separate Client record, the Organisation is created independently and linked to relevant People.

Powered Now Jobs are the primary mapping challenge. Each Job migrates as a Pipedrive Deal, with the Job name becoming the Deal name, the job status (Quoted, In Progress, Complete, Invoiced) mapped to Pipedrive pipeline stages, and the assigned engineer or team stored in a custom Person field on the Deal. Job notes and line items are preserved in the Deal's description and custom item fields respectively.

In Powered Now, Quotes are standalone objects linked to Jobs. During migration, Quote data merges into the Deal record as line items (products and pricing) and a total value field. The quote validity date migrates as a custom datetime field on the Deal for reference. If the Quote is not yet accepted, the Deal lands in an early pipeline stage (e.g., 'Quote Sent').

Invoices carry MTD-relevant data (VAT registration, invoice number, tax amounts) that has no Pipedrive equivalent. FlitStack AI migrates the commercial summary — client, amount, date, status — as Deal fields and a custom Invoice_Number__c field. The full invoice record with line-item tax breakdown is exported as a structured CSV for import into Xero or your accounting tool.

Powered Now diary entries (scheduled jobs, engineer appointments) map to Pipedrive Activities. Each entry becomes a Task or Event with the job context stored in the activity's subject and a link back to the migrated Deal. Pipedrive Activities do not support engineer scheduling across multiple resources natively — complex diary data is also exported as a reference file.

Certificates (gas safety, electrical compliance, etc.) are a Powered Now-specific object with no Pipedrive equivalent. Migration options are: (a) store certificate metadata (type, expiry date, engineer) as custom fields on the associated Deal, (b) attach the certificate PDF as a Pipedrive File linked to the Deal, or (c) export certificates to a separate structured file for compliance record-keeping.

Purchase Orders reference supplier costs against a job. PO number, supplier name, and total amount migrate as custom fields on the Deal. Full PO line-item detail is exported separately, as Pipedrive has no PO object. FlitStack AI can optionally link PO data to a separate Products catalogue if your Pipedrive plan includes it.

Supplier invoices are expense records with no Pipedrive equivalent. FlitStack AI exports these as a structured CSV alongside the migration, tagged with the corresponding Deal reference so the data can be imported into Xero, QuickBooks, or your accounting tool post-migration.

Powered Now custom properties on clients and jobs — engineer assignment, site type, certification required, custom pricing tiers — are created as Pipedrive custom fields on the corresponding object (Person, Organisation, or Deal) before migration. Pipedrive's API assigns a 40-character hash key to each custom field, which FlitStack AI resolves during the import mapping phase.

Powered Now users (engineers, office staff) are resolved by email match against Pipedrive Users. Unmatched users are flagged before migration. Inactive Powered Now users are imported as inactive Pipedrive users with a note; you decide whether to activate them post-migration.