Migrate your Estimate Rocket data

Clients in Estimate Rocket hold contact info, billing address, and internal notes. All current and historical projects are accessible from the Client record. We import Clients as Contacts, preserving project history as a custom property if the destination has no linked Projects object.

Projects are the central entity tying Estimates, Work Orders, Invoices, and Schedule entries together. We migrate Projects 1:1 and map their status (All, Late, Today, Future) to the destination's equivalent pipeline stage model.

Estimates carry line items, descriptions, discounts, and a configurable approval workflow. The June 2024 API added a dedicated Proposals endpoint. We map Estimate line items to destination quote or proposal line items, preserving Units, Unit Price, Unit Cost, Section, Type, and Taxable flags.

Work Orders follow estimates and contain scheduled assignments, field-user notes, and final costing. We preserve Work Order-to-Estimate linkage and carry forward Work Notes as internal notes in the destination system.

Items are the price-list catalog: Name, Units, Description, Unit Price, Unit Cost, Section, Type (material/labor), Taxable flag, and Work Notes. We import Items into the destination's product or service catalog, mapping Type to the correct category and preserving costing for margin reporting.

Invoices are generated from Projects and may carry open or paid status, line items, and payment history. We map Invoice line items to the destination's billing records, but payment history and aged AR must be manually reconciled post-migration since invoice IDs do not transfer between systems.

Schedule entries are calendar events linked to Projects, Estimates, or Work Orders with assigned users and due dates. We map Schedule entries to the destination's calendar or task objects, but recurrence patterns and drag-and-drop position do not carry over.

Estimate Rocket tracks time per project and work type per user. Time entries include clock-in/clock-out and are reviewable by field users. We migrate Time Entries as time-logged records linked to the corresponding Project.

Users are assigned as Owners or Field Users (with separate pricing tiers). We map Users to destination users and flag Field Users separately for review, as role semantics differ across CRMs.

Email Templates use tokens that pull data directly from the Estimate Rocket database. Token-based templates do not transfer directly to other CRMs; we document which templates exist and recommend rebuilding them using the destination's merge-field syntax post-migration.

Follow-up Campaigns are a series of automated emails configured per project phase in Estimate Rocket. These automation rules are stored in the platform's own workflow engine and cannot be exported. We skip them and flag campaign sequences for manual recreation in the destination system.

Estimate Rocket logs every user action inside the app under Activity History. This is an audit trail, not a transactional record. We do not migrate Activity History as a primary object; we note its existence and advise customers it stays in the source system.