Migrate from The Customer Factor to Microsoft Dynamics 365 Sales

The Customer Factor customer maps directly to a Dynamics 365 Account. Company name becomes Account.Name; address, phone, email, and website fields map to standard Account fields. Parent-company hierarchies, if used in The Customer Factor, map to Account.ParentAccountId. Any related contacts are linked via the Account.Contacts relationship, preserving the full contact history from the source system.

The Customer Factor prospect has no explicit lifecycle stage — every prospect is a contact record. We split on a decision: prospects with a converted estimate or job route to Contact on an Account; unconverted prospects route to a Dynamics 365 Lead so the sales team can work the qualification process normally.

The Customer Factor estimate is a header record with line items. It maps to a Dynamics 365 Opportunity with the estimate total as the Opportunity.Amount and each line item as an OpportunityProduct record with product name, quantity, and unit price. The Estimate.ID is preserved in a custom Source_Estimate_ID__c field for traceability.

Jobs are the core transactional record in The Customer Factor. They map to Opportunities where job status maps to a stage name (e.g., Scheduled, In Progress, Completed), the estimated amount maps to Amount, and the actual billed amount is stored in a custom Job_Actual_Amount__c field. The job's linked customer becomes the Opportunity's Account lookup.

The Customer Factor invoice references a job and carries total amount and status. In Dynamics 365, the invoice is represented by the Opportunity that the job created; the invoice number and paid status are stored as custom fields on that Opportunity so reporting stays tied to the deal record.

The Customer Factor owner ID resolves to a Dynamics 365 SystemUser by email match. Unmatched owners are flagged before migration — your team either invites them to Dynamics 365 first or assigns their records to a fallback owner. No record lands without a valid OwnerId.

Every The Customer Factor custom field gets a new column in Dataverse. The schema name appends _cf (e.g., job_type becomes job_type_cf). The field type is assessed at migration time against Dataverse-supported types — pick-lists, decimals, and date fields are all migratable; unsupported types are flagged before the schema is built.

The Customer Factor file attachments on customers, jobs, and invoices have no native Dynamics 365 equivalent at the file-storage level. We re-upload files to Dynamics 365 Notes or to an associated SharePoint document library linked to the Account or Opportunity, preserving the original filename and upload date.

The Customer Factor items or services used on estimates and jobs map to Dynamics 365 Products. Each product gets a name, unit price, and product type (sales item vs. service). If The Customer Factor uses a flat item list, we create corresponding Products in Dynamics 365 before linking them to migrated OpportunityProduct records.

The Customer Factor appointment with subject, scheduled date, duration, and linked customer or job maps to a Dynamics 365 Appointment record. The original scheduled date and duration are preserved; the appointment is linked to the Account or Contact that resulted from the customer migration.