Migrate from RealGreen by WorkWave to Pipedrive

RealGreen Customer maps directly to Pipedrive Person. The Person record stores name, email, phone, address, and owner assignment. FlitStack resolves owner by matching the customer's assigned owner email to a Pipedrive user. Multiple phone numbers on a RealGreen customer (home, mobile, work) map to the primary phone field and a secondary custom field.

RealGreen Properties (service locations with address, property type, and measurement data) map to Pipedrive Organizations. The Organization stores the property address, site name, and industry classification. Multi-crew companies with multiple service locations produce multiple Organization records linked to the same Person if needed via relationship fields.

RealGreen Work Orders contain service type, property link, status, amount, and date. These map to Pipedrive Deals — the Deal holds monetary value and stage. RealGreen work-order status (Scheduled, In Progress, Completed, Invoiced) maps to Pipedrive Deal stage values. Each work order becomes one Deal; historical work orders land as closed-won Deals with original completion date preserved as a custom field.

RealGreen estimates with line items (service type, quantity, price) map to Pipedrive Deals with attached Products. The estimate total becomes the Deal value. Pipedrive's Products feature stores the individual line items that made up the estimate. FlitStack creates the Pipedrive Product records from RealGreen estimate line items before attaching them to the Deal.

RealGreen invoices (linked to work orders, with payment status and amount) map to closed Deals with custom fields for invoice_number, invoice_amount, and payment_status. The payment_status field captures whether the invoice was Paid, Pending, or Overdue in RealGreen at migration time. Actual payment processing history (via WorkWave Payments) does not migrate since Pipedrive has no payment processing module.

RealGreen service history entries (date performed, service type, crew, notes) map to Pipedrive Activity records (type = task, subject = service type, due_date = service date). Original crew notes and service details migrate as Activity notes. This preserves the full service audit trail in the contact's activity timeline.

RealGreen flag codes (BALD, TREE, IRRIG, CHEM, MOW, LAND, etc.) are green-industry property classification tags. Pipedrive has no native flag-code equivalent. FlitStack creates a custom pick-list field (RG_Flag_Code__c on Organization) and maps each RealGreen flag code value-by-value. Multiple flag codes on a property are stored as a comma-separated string in the custom field.

RealGreen service types (Mowing, Aeration, Fertilization, Tree Care, Irrigation, etc.) are service classification fields. Pipedrive Deals have no native service-type field. FlitStack creates a custom pick-list field (RG_Service_Type__c on Deal) with value-mapping from the RealGreen service type list. Deals can then be filtered by service type in Pipedrive's list view.

RealGreen payment transactions (autopay enrollment, payment method, pay-over-time status) have no Pipedrive equivalent. We preserve payment method, autopay flag, and pay-over-time eligibility as custom fields on the Deal record. Actual transaction history and tokenized card data from WorkWave Payments does not migrate and must be re-established with a new payment processor if needed.

RealGreen dynamic routing and crew scheduling data has no Pipedrive equivalent. Routes, dispatch assignments, and schedule optimization do not migrate. Teams should evaluate dedicated routing tools (Route optimizer, Jobber, or Lavoro) if routing is a core operational requirement after leaving RealGreen.

RealGreen's Customer Assistant website settings, self-service portal preferences, and communication automation rules are platform-specific configurations. Pipedrive has no customer portal module. These settings must be recreated manually or through Pipedrive's Marketplace apps if equivalent functionality is needed. FlitStack documents the current portal settings during the audit phase so your team has a reference for manual rebuild.