Migrate from RealGreen by WorkWave to Microsoft Dynamics 365 Sales

RealGreen customer records map 1:1 to Dynamics 365 Accounts. The Account Name, primary contact, billing address, phone, and email fields transfer directly. Account category codes (Residential, Commercial, HOA) are preserved via option‑set values. For multi‑location customers, each service location becomes a separate Account record keyed by its address, while a parent‑account lookup links them when hierarchical data is available.

RealGreen stores primary and secondary contact information on each customer. These map to Dynamics 365 Contacts linked to the Account via the AccountId lookup. Each Contact record receives the full name, job title, email, phone, mobile phone, and preferred contact method. Additional custom fields on the RealGreen contact are migrated as custom columns on the Contact entity, preserving data types and option‑set values.

RealGreen's Property records carry property-specific fields (lawn type, gate code, irrigation flags, lot size, access notes). Dynamics 365 has no native Property entity. We create a custom Property__c table (or use location-specific Account records) and map property fields as custom columns on that table.

Work orders are the core RealGreen object — they link customer, property, service type, crew, schedule, line items, and completion notes. We map work orders to Dynamics 365 Cases (Incident table) and preserve the work order number as a custom field. Service type maps to Case Title; crew and schedule data map to custom fields on the Case.

Service tickets in RealGreen map directly to Dynamics 365 Cases. The ticket number becomes a custom Source_Ticket_ID__c field on the Case. Ticket status (Open, In Progress, Resolved) maps to the Case Status option set, and resolution notes map to the Case Description or a custom resolution field.

RealGreen estimates contain line items, pricing, and proposal text. Each estimate becomes a Dynamics 365 Opportunity with an associated Quote. Line items map to Opportunity Product rows using the Product Catalog. Proposal text migrates to the Opportunity Description or an attached Note. Estimate status (Sent, Accepted, Declined) maps to Opportunity Stage.

RealGreen service types and price-list items map to Dynamics 365 Products. Each service line item in an estimate or work order becomes a Product record with a unit price. Product families can represent service categories (e.g., Lawn Care, Irrigation, Tree Service).

Dynamic routing data — stop sequence, crew assignments, GPS coordinates, and time-window constraints — has no native Dynamics 365 equivalent in the base Sales app. We export this as a CSV reference file for your admin. If you deploy Dynamics 365 Field Service, routing maps to Bookable Resources and Resource Scheduling Optimization (RSO) records.

RealGreen equipment records (mower types, irrigation systems, maintenance history) have no direct counterpart in Dynamics 365 Sales Professional. We map these to a custom Asset__c table on Dataverse linked to the Account or Property record. If Field Service is deployed, native Asset records apply.

WorkWave payment records, card transactions, and autopay enrollment cannot migrate as operational Dynamics records without Business Central. We map the total paid amount from closed work orders to the Opportunity Amount field for revenue tracking and export payment history as a CSV for Business Central import if applicable.

RealGreen allows per-customer custom properties (e.g., preferred contact method, contract type, flag codes). Each custom property becomes a custom column on the Account table in Dataverse. Data type is preserved: text fields map to Text, numeric fields to Decimal or Whole Number, date fields to Date.

Property-level custom fields such as irrigation zone, slope type, sun exposure, and HOA restrictions migrate as custom columns on the Property__c table we create in Dataverse. Each field maps to the matching Dataverse data type: text fields become Text columns, numeric fields become Decimal or Whole Number, and pick‑list values become Option Set fields. Property records link to the parent Account via the AccountId lookup to preserve the customer‑property relationship.

RealGreen user IDs resolve by email match against Dynamics 365 SystemUser records. Crew leaders, dispatchers, and account managers map to the OwnerId field on Accounts, Contacts, Cases, and Opportunities. Unresolved users are flagged before migration and assigned to a fallback owner.