Migrate from Estimate Rocket to Microsoft Dynamics 365 Sales

Estimate Rocket Clients with a company name map directly to Dynamics 365 Accounts. The account's primary address, phone, and website transfer as AddressLine1, Telephone1, and WebSiteURL. Clients flagged as individuals without a company name are split into Account (for address) plus a Contact record.

Estimate Rocket Clients stored as individual contacts (without a company association) migrate as Dynamics 365 Contacts. The Contact's parent AccountId links to a default 'Unassigned' Account record or to a matching company-type Client record that also migrated, preserving the person-to-company relationship.

Estimate Rocket Projects map to Dynamics 365 Opportunities. The project name becomes the Opportunity Name, estimated value maps to EstimatedValue, and project status (Active, Completed, Lost) determines the Opportunity Stage value selected from the mapped stage pick-list. One Estimate Rocket Project = one Dynamics 365 Opportunity.

Estimate Rocket Estimates with status Draft or Sent migrate as Dynamics 365 Quotes. Each estimate line item becomes a Quote Detail (quotedetailid) linked to the Quote and to a Dynamics 365 Product record representing the Estimate Rocket Item. Original estimate date and expiry date transfer to quotedate and expiringdeliverydate respectively.

Estimate Rocket Proposals accepted by a client split into two outcomes: the proposal body migrates as a Dynamics 365 Quote, and the resulting work scope creates a linked Opportunity representing the Project. Accepted Proposals that have already generated Work Orders are flagged so the Opportunity Stage reflects 'Won – In Progress' rather than a standard closed stage.

Dynamics 365 Sales has no native Work Order entity. Estimate Rocket Work Orders are captured as a custom field set (Work_Order_Number__c, Work_Order_Status__c) on the linked Opportunity, plus a Task record series for key milestones. Clients requiring full work-order management are directed to Dynamics 365 Field Service as a separate module.

Estimate Rocket Items from the item catalog map 1:1 to Dynamics 365 Products with product type 'Sales Item' for materials and 'Service' for labor entries. Unit of Measure transfers to defaultunitid, and unit price becomes the default pricelevel amount. Items with cost data populate the standardcost field for margin reporting.

Estimate Rocket Schedule entries (calendar appointments linked to Projects) migrate as Dynamics 365 Appointments with the original start/end times, subject line, and assigned user resolved by email match. Schedule entries without a time (task-style assignments) migrate as Tasks. Dynamics 365 Field Service scheduling boards require a separate license and are not included in this migration.

Estimate Rocket files attached to Estimates, Proposals, or Projects are downloaded and re-uploaded as Dynamics 365 Note (annotation) records with the original file name and MIME type preserved. Files exceeding Dynamics 365's 25MB default per-file limit are flagged for chunked upload or alternative storage links.

Estimate Rocket users are matched to Dynamics 365 system users by email address. Unmatched users are flagged before migration so the team either invites them to Dynamics 365 or assigns their records to a fallback owner. Role and permission sets are not migrated — those are destination-side configuration.

Any custom fields configured on Estimate Rocket Clients, Projects, Estimates, or Items are enumerated during the pre-migration audit. Each custom field is created as a custom column on the corresponding Dynamics 365 entity using the __c suffix convention, with data type matched (text, number, picklist, checkbox). No custom objects exist in Estimate Rocket equivalent to Dynamics 365 custom tables.

Estimate Rocket Invoices migrate as Dynamics 365 Invoices when the source system contains historical invoice records. The Invoice is linked to the parent Quote and Opportunity so Dynamics 365's revenue reporting reflects the won deal. Active invoicing should continue in Estimate Rocket until cutover; the migration captures the snapshot as of the delta window.