Migrate from Estimate Rocket to Salesforce Sales Cloud

Estimate Rocket clients map to Salesforce Accounts for company-level data (name, address, billing info) and primary Contact records for the main point of contact. Multiple Estimate Rocket contacts per client create additional Salesforce Contact records linked via AccountId. We resolve primary contact using Estimate Rocket's primary-contact flag.

Estimate Rocket projects map to Salesforce Opportunities with a Project_Flag__c custom checkbox set to TRUE. This flags the record as a migrated project rather than a standard sales opportunity. The project name becomes Opportunity.Name, project value maps to Amount, and project status (Active/Closed) maps to Opportunity.StageName via value mapping.

Estimate Rocket estimates map to Salesforce Quotes linked to the corresponding Opportunity. A custom Estimate__c object holds Estimate Rocket-specific fields: Estimate_Number__c, Section_Tax_Rate__c, and Discount_Pct__c. Standard Salesforce Quotes do not support section-level tax calculation — this is handled via custom fields on the Quote object.

Estimate Rocket items (materials and labor line items) map to Salesforce Product2 records. Unit Price maps to Salesforce's ListPrice on PricebookEntry. Item fields — Unit_Cost__c, Markup_Pct__c, Taxable__c, Item_Type__c (material/labor), and Section__c — migrate as custom fields on Product2. Each Product2 receives a PricebookEntry for the standard price book.

Estimate Rocket work orders map to Salesforce Tasks with a custom Work_Order__c lookup linking back to the Project Opportunity. Task.Subject carries the work order title, Task.ActivityDate carries the due date, and Task.Status maps from Estimate Rocket work order status (Scheduled/In Progress/Complete). Custom Work_Order__c fields hold work-order-specific data: Work_Order_Number__c and Scope__c.

Estimate Rocket calendar entries map to Salesforce Events. Event.Subject holds the appointment title, Event.StartDateTime and EndDateTime preserve the original schedule time, and Event.WhatId links to the related Project Opportunity. Custom Schedule_Entry__c fields capture Assignee__c (assigned team member) and Schedule_Type__c (estimate visit/work order execution).

Estimate Rocket time tracking entries map to Salesforce Tasks with a custom Time_Entry__c object. Custom fields on Time_Entry__c include Hours__c, Billable__c, and Work_Type__c (material/labor/mileage). OwnerId resolves by email match to the corresponding Salesforce user. Time entries without a matching Salesforce user are flagged for manual assignment.

Estimate Rocket invoices map to Salesforce Orders linked to the Project Opportunity. A custom Invoice__c object holds Invoice_Number__c, Invoice_Date__c, and Balance_Due__c. Note: Estimate Rocket invoices contain payment history — this migrates as OrderLineItem with payment status custom fields. Salesforce's native invoicing module is not used; custom Invoice__c + Order handles the record.

Estimate Rocket file attachments (images, PDFs, signed documents) migrate as Salesforce Files — ContentVersion holds the binary, and ContentDocumentLink associates the file to the parent record (Account, Opportunity, or Work_Order__c) via LinkedEntityId. Salesforce's 25MB per-file limit applies; large files are flagged for pre-migration review.

Estimate Rocket email templates have no Salesforce equivalent — templates use tokens that reference Estimate Rocket field names not present in Salesforce. We export the full template definitions (HTML body, subject, token list) to a JSON reference file. Your Salesforce admin rebuilds these in Salesforce Email Templates or a third-party email tool like Salesloft or Outreach.

Estimate Rocket follow-up campaigns (automated email sequences tied to project milestones) cannot migrate to Salesforce as native objects. We export the campaign configuration — trigger conditions, email sequence, delay intervals — as a rebuild reference. Salesforce Campaigns handle list-based email but not milestone-triggered sequences; these require Flow + a separate email-automation tool.

Estimate Rocket allows custom fields on line items (e.g., Color_Code__c, Manufacturer__c, Warranty_Months__c). These migrate as custom fields on the Product2 object with the __c suffix. Field type mapping: text fields become Text(255), numeric fields become Number, date fields become Date. Pick-list fields on Estimate Rocket items map to Salesforce custom pick-lists with value-by-value mapping.