Migrate from RealGreen by WorkWave to Odoo CRM

RealGreen customer records map directly to Odoo res.partner. The customer name, primary contact info, billing address, and account status all map to standard res.partner fields. We create one res.partner record per RealGreen customer as the top-level record; location-specific addresses attach as child contact records on the same partner.

A key structural difference: RealGreen allows multiple service locations per customer, each with its own address and service setup. Odoo res.partner stores address on the partner record itself. We split each RealGreen location into a separate Odoo contact record (type=contact) linked to the parent customer partner via the parent_id field, preserving the address and location-specific service program assignments.

RealGreen work orders map to Odoo crm.lead opportunities. The work order name and description become the opportunity name and description. Work order status (Scheduled, In Progress, Completed, Invoiced) maps to Odoo stage values. Location links to the corresponding Odoo location-contact partner. Scheduled dates, crew, and pricing map to the opportunity's date, user, and expected revenue fields.

RealGreen owner and sales rep fields resolve to Odoo res.users by email address match. We query Odoo users during planning and flag any owner without a corresponding Odoo login. Unmatched owners are assigned to a designated fallback Odoo user, and the original RealGreen owner name is preserved in a custom field for audit continuity.

RealGreen service programs represent recurring service packages (e.g., Weekly Lawn Care, Monthly Landscaping, Quarterly Pest Control) assigned per location. These have no direct Odoo equivalent. We create a custom selection field on crm.lead capturing the service program type and map each location's assigned program from RealGreen into this field, preserving the service history on each opportunity.

Each RealGreen location address — street, city, state, ZIP, country — maps to the corresponding fields on the Odoo child contact record. Latitude and longitude coordinates from RealGreen are preserved as custom float fields on the contact since Odoo does not have native lat/long storage at the address level.

RealGreen call logs, email threads, and SMS records attached to a work order migrate as Odoo mail.message records linked to the crm.lead. Original timestamps and content are preserved. Inline images and attachments are downloaded and reloaded as Odoo attachments linked to the same message thread, maintaining the full service communication history.

RealGreen flag codes are internal status markers used by operations teams to flag accounts for specific handling (e.g., priority customers, disputed accounts, billing issues). Odoo has no native equivalent. We create a custom selection field on crm.lead and map each work order's flag codes from RealGreen into this field, allowing your Odoo team to continue using the same operational signals post-migration.

RealGreen file attachments — photos, signed forms, PDF proposals — migrate to Odoo ir.attachment records linked to the corresponding crm.lead opportunity or res.partner contact. File size limits per Odoo configuration apply; we chunk large batches to stay within limits. Inline images embedded in work order notes are extracted and stored as separate attachments.

The original RealGreen customer ID and work order ID are preserved in custom fields on the Odoo records (e.g., realgreen_customer_id__c and realgreen_workorder_id__c). These IDs enable delta-run de-duplication, traceability back to source records, and audit reporting against the original dataset throughout the migration process.

RealGreen stores equipment and asset records for customer properties (e.g., irrigation systems, hardscape features). Odoo does not have a native asset management module in the base CRM app. We migrate these as product.product records flagged as assets, with a custom is_asset boolean field. Full asset lifecycle management would require Odoo's Asset Management module as a separate implementation step.

RealGreen Dynamic Routing data — crew assignments, route stops, GPS tracks, and scheduled visit sequences — is green-industry-specific and has no Odoo CRM equivalent. We preserve crew name and route identifier in custom fields on the work order opportunity, but route optimization logic must be rebuilt in Odoo using a third-party routing integration or custom development.