Migrate from Powered Now to Microsoft Dynamics 365 Sales

Powered Now clients with company names map directly to Dynamics 365 Sales Account.Name. Sole-trader clients with personal names map to Account.Name with Contact created as the primary Contact record. Primary address and postcode map to Account.Address fields.

Client contact details — name, email, phone — map to Dynamics 365 Sales Contact.FirstName, Contact.LastName, Contact.Email, Contact.Phone. Multiple contacts per client create multiple Contact records linked by AccountId lookup.

Powered Now jobs translate to Dynamics 365 Sales Opportunity records. Job name becomes Opportunity.Name. Job status (Quoted, In Progress, Complete, Invoiced) maps to Opportunity StageName pick-list values. Job value maps to Opportunity.Amount. Close date is derived from job completion date.

Powered Now quotes map 1:1 to Dynamics 365 Sales Quote entities. Quote number becomes Quote.Name. Line items (labour, parts, call-out fee) map to Quote Product records with Quantity, UnitPrice, and manual VAT calculations.

Powered Now invoices map to Dynamics 365 Sales Invoice records. Invoice number becomes Invoice.Name. Line items map to Invoice Product records. VAT amount and Making Tax Digital status are preserved as custom columns on the Invoice.

Dynamics 365 Sales has no native Purchase Order object in the base CRM schema. Supplier purchase orders migrate as a custom Dataverse table with PO number, supplier link, line items, and status — created as part of the migration schema setup.

Powered Now diary entries with engineer assignments translate to Dynamics 365 Sales Task records with Subject, ScheduledStart, and OwnerId resolved by engineer email. Job-site postcode and What3Words reference preserved as custom text fields.

Supplier invoices from Powered Now have no direct Dynamics 365 Sales equivalent. We create a vendor-invoice custom entity mapping supplier name, invoice number, amount, date, and status — accessible for reconciliation reporting in Power BI post-migration.

Powered Now certificates for gas safety and electrical work cannot be generated by Dynamics 365 Sales. We migrate certificate records as Note attachments on the associated Job/Opportunity, with certificate type, expiry date, and engineer name preserved as custom fields for compliance tracking.

Powered Now custom fields on clients (e.g., trade classification, account tier, credit limit) migrate as custom columns on the Account table in Dataverse, using the new_ prefix naming convention. Field type constraints applied per Dynamics 365 Sales data model.

Powered Now custom fields on jobs (e.g., job type, priority flag, site-access notes) migrate as custom columns on the Opportunity table. Text, number, date, and pick-list types are supported; pick-list values require value-mapping setup in the migration plan.

Powered Now team members are resolved by email match to existing Dynamics 365 Sales users. If no match exists, the team member is flagged as an unassigned owner — your admin either creates a Dynamics user or assigns records to a fallback owner before migration runs.