Migrate from RealGreen by WorkWave to HubSpot

RealGreen customer accounts map directly to HubSpot Companies. The primary contact, billing address, and service address all map to HubSpot company properties. Multi-location customers with branch offices may need hub-spoke setup in HubSpot or multiple company records linked by a parent field.

RealGreen contact records (the named individuals at a customer account) map 1:1 to HubSpot Contacts. Email, phone, mobile, job title, and address fields map to HubSpot's standard contact properties. A contact must be associated with a Company record via the HubSpot associations model.

RealGreen work orders (service records with date, crew, service type, and status) map to HubSpot Deals. The work order number becomes the deal name; the scheduled service date becomes the deal close date; the service type and status map to deal pipeline stage values. Multiple work orders for the same customer roll up to a single deal or spawn individual deals per your specification.

RealGreen work order line items (individual services rendered: mowing, aeration, fertilization) have no native HubSpot equivalent. We create a custom deal-line-item structure using HubSpot custom properties or a custom object — service name, quantity, price, and notes are preserved per line.

RealGreen service tickets (support or callback requests tied to a customer) map to HubSpot Tickets. Ticket subject, description, status, priority, and owner carry over. Ticket pipelines in HubSpot replicate the ticket status flow from RealGreen. Any attachments or internal notes on the ticket migrate as HubSpot engagement logs linked to the ticket record.

RealGreen payment records (transaction amount, method, date, status) from WorkWave Payments have no native HubSpot equivalent. We map them to a custom payment-history object linked to the HubSpot Deal or Company — this preserves financial context without cluttering deal records.

RealGreen flag codes are categorical tags on customer records (priority customer, no soliciting, gated community, etc.) used by crews in the field. These migrate as a multi-select custom contact property in HubSpot. The full list of flag codes is extracted from RealGreen and mapped value-by-value.

Custom PDF proposals, contracts, and digital forms created in RealGreen Forms cannot be auto-converted to HubSpot forms due to PDF-specific logic and dynamic field bindings. We export the form content as a PDF attachment linked to the relevant HubSpot record. HubSpot forms must be rebuilt separately.

RealGreen's dynamic routing data (crew name, route order, GPS stops) has no HubSpot equivalent. We preserve routing context as reference text on the contact or deal record — crew and service date are migrated; turn-by-turn route geometry is not applicable in a CRM context.

RealGreen's Customer Assistant portal sessions (autopay enrollments, invoice view history, portal logins, self-service schedule changes) have no HubSpot equivalent. This data cannot be migrated programmatically. We document portal configuration so your team can recreate autopay enrollment and self-service settings in your chosen HubSpot payment integration or billing connector post-migration.

RealGreen's built-in email marketing campaigns (drip sequences, seasonal promotions) use a proprietary campaign structure. Campaign names, subject lines, and send dates migrate as a reference log. The actual marketing automation logic must be rebuilt in HubSpot's marketing hub using workflows and lists.

RealGreen users (office staff, dispatchers, crew leads) resolve by email match against HubSpot users. Unmatched users are flagged before migration — your team either creates HubSpot accounts first or assigns records to a fallback owner. Crew-level users who won't have HubSpot access are mapped to a designated dispatcher owner.