Migrate from Estimate Rocket to Pipedrive

Individual contacts in Estimate Rocket map directly to Pipedrive Person records. Name, email, phone, and address fields migrate as direct equivalents. If the client record contains a company name in a separate field, FlitStack creates a corresponding Organization and links it to the Person via the org_id field in Pipedrive's Person object. Unmatched email addresses are flagged before the migration commits.

When an Estimate Rocket Client record includes a company name, FlitStack creates a Pipedrive Organization for that company and links the Person to it. Address data from Estimate Rocket's Client record migrates to the Organization's address fields. Invoices and billing contacts on the company level surface on the Organization record in Pipedrive.

Each Estimate Rocket Project becomes a Pipedrive Deal. The project name maps to Deal title (name field), the current project status maps to a custom Project_Status__c pick-list field, and the project address migrates to the Organization's address or a custom Address__c field on the Deal. Project create dates are preserved as Original_Create_Date__c on the Deal for reporting continuity.

Estimate Rocket Estimates do not have a native Pipedrive equivalent — Pipedrive handles quotes via the separate Smart Docs product, which is not part of core CRM data. FlitStack migrates the estimate amount, line items, and discount % as custom fields on the Deal: Estimate_Amount__c, Discount_Pct__c, and Estimate_Sent_Date__c. This preserves the estimate history within the Deal record so sales teams can see original estimate values alongside the negotiated deal value.

Work Order records in Estimate Rocket map to the same Deal as the parent Project — the Work Order status, scheduled date, and assigned user migrate as custom Deal fields: Work_Order_Status__c, Work_Order_Scheduled_Date__c, and Work_Order_Assigned_User__c. This prevents duplicate Deal records while preserving the full operational history of each job.

Estimate Rocket Items (materials and labor) map to Pipedrive Products with name, unit price, unit cost, and taxable flag preserved. Each Product is then linked to the corresponding Deal via the Deal-Product association in Pipedrive. Taxable status is stored as a custom flag on the Product record. Items without a linked Deal are imported as standalone Products for later association.

Estimate Rocket Schedule entries and Assignments map to Pipedrive Activities. A scheduled work order appointment with a specific date and time becomes a Pipedrive Event with start/end timestamps and the assigned team member as the activity owner. One-off scheduling notes without a fixed time become Pipedrive Tasks with a due date. Original scheduling notes migrate as activity notes for reference.

Estimate Rocket internal notes and project activity history migrate as Pipedrive Notes attached to the corresponding Person, Organization, or Deal. Original timestamps and the creating user's name are preserved in the Note record. Notes are imported via the Pipedrive Notes API endpoint to maintain proper parent-record associations.

Estimate Rocket file attachments on projects or clients are downloaded and re-uploaded as Pipedrive Activity attachments. Pipedrive's default file size limit is 50 MB per attachment. Files exceeding this limit are flagged in the migration report and your team decides whether to compress, split, or exclude them. Inline images in Estimate Rocket notes are extracted and rehosted.

Estimate Rocket users and field users are matched to Pipedrive users by email address. Field users (who pay $10/mo in Estimate Rocket) are reclassified as standard Pipedrive users during migration — Pipedrive does not have a separate field-user role with different pricing, so your Pipedrive admin assigns them standard seat types based on your plan. Unmatched users are flagged for team invite before the migration runs.

Estimate Rocket custom fields created through the Customize Fields section migrate as Pipedrive custom fields using the corresponding field type (text, number, date, picklist, or checkbox). Pipedrive custom fields are referenced by hash-based keys in the API, so FlitStack creates the custom fields in Pipedrive first and maps the keys before writing data. Any pick-list custom fields in Estimate Rocket are recreated as Pipedrive pick-list options with value-by-value mapping.

Estimate Rocket's Intelligent Insight Reports and project profitability dashboards are source-side schema constructs that do not have a direct Pipedrive equivalent. FlitStack migrates all underlying data — project costs, line-item profitability, team performance metrics — as custom fields on Deals, People, and Organizations. Your Pipedrive admin rebuilds the report layouts in Pipedrive's built-in reporting or exports the data to a BI tool for analysis.