Migrate from RealGreen by WorkWave to Freshsales

RealGreen Active Customers map to Freshsales Contacts with a linked Account (the customer's business entity). We extract the primary contact name, address, phone, and email, then create a corresponding Account record for the business address or company name. Customers without a company name create individual Contact records with no Account link.

RealGreen Marketing Records — prospects in the pipeline without active service — route to Freshsales Leads. This separates pre-service prospects from active customers in Freshsales' lifecycle model. The Lead stores contact details, source information, and any marketing campaign attribution from RealGreen.

Work Orders in RealGreen represent service events tied to a customer and a crew. These map to Freshsales Deals with service-specific metadata (work order number, service date, crew assignment, service type) stored as custom fields on the Deal. The Deal amount reflects the work order value or estimate.

RealGreen service history records capture detailed operational data including dates of service performed, specific services rendered (such as mowing, tree trimming, or irrigation repair), crew notes documenting field observations, and technician signatures. These attach as custom fields on the corresponding Freshsales Contact or Deal. Historical service counts and last-service-date are preserved as numeric and date fields respectively for reporting purposes.

RealGreen flag codes signal customer status indicators (e.g., payment issues, priority accounts, no-contact flags). These map to a Freshsales custom pick-list field (RG_Flag_Code__c) with the exact flag-code values preserved. Teams configure Freshsales views and workflows based on these values post-migration.

RealGreen service programs cover multiple green-industry verticals including lawn care, landscaping, arbor care, irrigation system maintenance, and snow removal services. These map to a Freshsales custom multi-select field (RG_Service_Programs__c). Customers enrolled in multiple service programs have all applicable values preserved in the single field, maintaining their complete service history.

RealGreen user accounts (office staff and crew leads) resolve to Freshsales agents by email address match. We flag any RealGreen owner without a corresponding Freshsales user and assign those records to a designated fallback owner until your team provisions the account.

RealGreen customer notes migrate to Freshsales Notes attached to the Contact record, preserving the original note text and creation timestamp. File attachments — signed forms from RealGreen Forms, PDF invoices, service photos, and other documents — are downloaded from RealGreen and re-uploaded as Freshsales Files, linked to the corresponding Contact or Deal record for complete documentation continuity.

RealGreen payment records — including payment method, last payment date, and outstanding balance — migrate as custom fields on the Contact (RG_Last_Payment_Date__c, RG_Payment_Method__c, RG_Account_Balance__c). Full payment transaction history is preserved as a PDF or CSV attachment if available from RealGreen.

RealGreen route and crew assignments tied to work orders become custom fields on the corresponding Freshsales Deal (RG_Route__c, RG_Crew_Assigned__c). These are informational only — Freshsales has no routing engine. Teams use these fields for reporting or reconfigure routing in a separate route-optimization tool.

Any RealGreen extended properties or custom data structures built in Service Assistant 5 map to Freshsales custom modules or additional custom fields on the Contact/Account/Deal. We document the source schema and destination plan before migration so your admin can pre-create the Freshsales fields.

RealGreen's Customer Assistant Portal access records have no Freshsales equivalent. We do not migrate portal login status, self-service session data, or customer portal preferences. The portal access must be re-provisioned by the customer in Freshsales or through a separate customer portal integration that your team selects and configures post-migration.