Migrate your RealGreen by WorkWave data

Customer accounts in SA5 include contact details, addresses, flag codes, service programs, branch associations, and payment preferences. We migrate full customer records via the Customer Import Utility CSV format. Duplicate detection logic at import time is preserved.

Work Orders link a Customer to a Service, a Schedule, a Route, and a Crew. SA5 tracks open/closed status, line items, and completion timestamps. We migrate historical work order records with all associations intact and preserve the status flag so destination reporting continuity is maintained.

Routes in RealGreen are optimized sequences of Work Order stops assigned to a Crew on a given day. Dynamic Routing logs capture optimization scores and stop sequence changes. We map Route records and their linked stop assignments, but dynamic routing engine metadata is treated as source-specific and mapped to destination route structures.

Crew records link one or more Employees to a Branch with a vehicle assignment. Employee-to-crew assignments vary by day in RealGreen's scheduling model, so we capture the employee roster at migration time and flag active crew compositions for remapping to destination user structures.

RealGreen Forms stores PDFs and signature records linked to Customer accounts and Work Orders. We migrate form metadata, linked customer/work order references, and signature capture records. Form PDF content is migrated as binary attachments; dynamic field pre-population logic is not carried forward.

WorkWave Payments stores payment transactions, ACH and card records, and tokenized customer payment methods. Payment token portability requires a WorkWave-managed token transfer request form. We migrate transaction history and flag tokenized payment methods that require this separate transfer workflow.

Multi-location businesses in RealGreen organize under Branches that own customers, crews, and routing data. We preserve branch assignments on customer and crew records so multi-branch operators maintain their org structure integrity in the destination system.

Service Programs define recurring service offerings with frequency, pricing tiers, and seasonal parameters. We map service program definitions and their linked customer assignments, noting that frequency rules (weekly, biweekly, monthly, seasonal) require destination-side configuration.

Automated Marketing Assistant (AMA) triggers drip campaigns based on customer service history and lifecycle flags. Campaign history, contact segment membership, and trigger rule definitions are migrated where schema permits; active drip sequences are mapped to destination campaign tools.

Customer self-service portal configuration includes autopay enrollment, card-on-file, and installment plan preferences. Portal account records link to customer accounts and require re-enrollment flows in the destination platform unless direct SSO/token migration is coordinated.

Flag codes in RealGreen are internal customer status tags used for segmentation, routing priority, and marketing filters. We migrate flag code assignments as custom Contact properties, noting that flag code semantics are customer-defined and require documentation review.