CRM migration
Field-level mapping, validation, and rollback between RealGreen by WorkWave and Salesforce Sales Cloud. We move data and schema; workflows are rebuilt natively in Salesforce Sales Cloud.
RealGreen by WorkWave
Source
Salesforce Sales Cloud
Destination
Compatibility
12 of 12
objects map 1:1 between RealGreen by WorkWave and Salesforce Sales Cloud.
Complexity
BStandard
Timeline
48–72 hours
Overview
RealGreen by WorkWave operates as a vertical field service platform built around Service Assistant 5, combining CRM, scheduling, dynamic routing, work orders, invoicing, and integrated payments for green industry operators. Its data model centers on Customer records linked to Properties, Work Orders, Routes, and Employees — with service history, equipment records, and invoice data stored as related data. Salesforce Sales Cloud structures its model around Account, Contact, Lead, Opportunity, Case, Task, and Event objects, with a robust custom field (__c suffix) and Record Type model for varying page layouts per business unit. We map RealGreen customers to Salesforce Accounts with related Contacts for primary stakeholders, RealGreen work orders to Salesforce Cases using a custom service-type Record Type, RealGreen routes to a custom Route__c object with linked RouteStop__c junction records, and RealGreen employee records to Salesforce Users resolved by email match. We preserve the full service history as CaseHistory and custom datetime fields. FlitStack uses the WorkWave API for data extraction and Salesforce Bulk API for high-volume ingestion, with scoped read access that keeps your team operational in Service Assistant 5 throughout the cutover window. Workflows, automations, and dynamic routing rules in RealGreen do not migrate — we export them as configuration documentation for your Salesforce admin to rebuild in Flow or a field service app.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a RealGreen by WorkWave object lands in Salesforce Sales Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
RealGreen by WorkWave
Customer
Salesforce Sales Cloud
Account + Contact
1:1RealGreen Customer maps to Salesforce Account as the primary company record. The primary contact on the customer record creates a linked Salesforce Contact with the IsPrimaryContact__c flag set. Multiple contacts per customer create additional Contact records with role designations in Account Contact Relations.
RealGreen by WorkWave
Customer Contact
Salesforce Sales Cloud
Contact
1:1RealGreen contact roles (billing contact, service contact, site contact) map to Salesforce Contact records linked via AccountId. The contact's role designation is preserved as a Role__c custom pick-list field on AccountContactRelation for multi-role contacts.
RealGreen by WorkWave
Property
Salesforce Sales Cloud
Account (secondary) or Custom Property__c object
1:1RealGreen property records (service location with lawn size, property type, gate codes) do not have a direct Salesforce equivalent. We map these to a custom Property__c object with a lookup to Account or create address-specific Account records when properties represent distinct billing entities.
RealGreen by WorkWave
Work Order
Salesforce Sales Cloud
Case (with RecordType=ServiceWorkOrder)
1:1RealGreen work orders map to Salesforce Cases using a custom Record Type named 'Field Service Work Order'. Work order line items map to CaseLineItem__c custom objects or Opportunity Products if the workflow involves sales quotes. Original work order number preserved as Origin_Work_Order_ID__c for traceability.
RealGreen by WorkWave
Work Order Status
Salesforce Sales Cloud
Case Status
1:1RealGreen work order statuses (Scheduled, In Progress, Completed, Invoiced, Cancelled) map to Salesforce Case Status values. The mapping requires a value-by-value pick-list alignment with your target Case Status values. Status change timestamps preserved as custom datetime fields.
RealGreen by WorkWave
Route
Salesforce Sales Cloud
Custom Route__c object with RouteStop__c junction
1:1RealGreen routes with ordered stops have no Salesforce native equivalent. We create a custom Route__c object linked to the routing date and crew, with a RouteStop__c junction object storing stop sequence, customer lookup, estimated arrival, and completion timestamps. This preserves the operational routing history for reporting.
RealGreen by WorkWave
Employee / Crew Member
Salesforce Sales Cloud
User
1:1RealGreen employee records map to Salesforce Users by email resolution. Active field employees get Salesforce Platform Licenses or Field Service licenses. Office staff map to Salesforce Sales reps. Unmatched employees are flagged for admin onboarding or fallback assignment before migration runs.
RealGreen by WorkWave
Equipment
Salesforce Sales Cloud
Custom Equipment__c object
1:1RealGreen equipment records (mowers, trailers, specialized tools linked to properties or routes) have no Salesforce standard object equivalent. We create a custom Equipment__c object with lookups to Account (owner) and Route__c (assigned route). Serial numbers and maintenance history preserved as custom fields.
RealGreen by WorkWave
Invoice / Payment Record
Salesforce Sales Cloud
Custom Invoice__c and Payment__c objects
1:1RealGreen invoice and payment history maps to custom Invoice__c and Payment__c objects linked to the Account. Invoice line items become InvoiceLine__c records. Payment method and transaction ID preserved for reconciliation. Note: payment token migration is out of scope per FlitStack policy.
RealGreen by WorkWave
Service History / Activity Log
Salesforce Sales Cloud
CaseHistory + Task/Event
1:1RealGreen service completion records map to Salesforce CaseHistory for status transitions. Detailed service notes and crew comments map to Tasks with Type='Service Note'. Original service completion timestamps and crew assignments preserved as custom fields for reporting continuity.
RealGreen by WorkWave
Flag Codes / Customer Tags
Salesforce Sales Cloud
Custom Pick-list on Account or AccountContactRelation
1:1RealGreen flag codes (priority customer, access issues, billing flags) used for operational routing and customer management map to a custom multi-select pick-list field FlagCodes__c on Account. These are informational flags, not Salesforce native flags or accounts.
RealGreen by WorkWave
Schedule / Appointment
Salesforce Sales Cloud
Event (linked to Case)
1:1RealGreen scheduled appointments map to Salesforce Events linked to the related Case via WhatId. Start and end times, technician assignment (WhoId to User), and service address preserved. Recurring service schedules documented as custom recurrence metadata for manual rebuild in Salesforce.
| RealGreen by WorkWave | Salesforce Sales Cloud | Compatibility | |
|---|---|---|---|
| Customer | Account + Contact1:1 | Fully supported | |
| Customer Contact | Contact1:1 | Fully supported | |
| Property | Account (secondary) or Custom Property__c object1:1 | Fully supported | |
| Work Order | Case (with RecordType=ServiceWorkOrder)1:1 | Fully supported | |
| Work Order Status | Case Status1:1 | Fully supported | |
| Route | Custom Route__c object with RouteStop__c junction1:1 | Fully supported | |
| Employee / Crew Member | User1:1 | Fully supported | |
| Equipment | Custom Equipment__c object1:1 | Fully supported | |
| Invoice / Payment Record | Custom Invoice__c and Payment__c objects1:1 | Fully supported | |
| Service History / Activity Log | CaseHistory + Task/Event1:1 | Fully supported | |
| Flag Codes / Customer Tags | Custom Pick-list on Account or AccountContactRelation1:1 | Fully supported | |
| Schedule / Appointment | Event (linked to Case)1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
RealGreen by WorkWave gotchas
WorkWave API requires paid developer account with setup and per-call fees
RealGreen was acquired by WorkWave in June 2021 — support and roadmap have shifted
Mobile app performance degrades after marking work orders complete
Snowflake Data Factory requires customer-managed compute costs
Tokenized payment methods require separate WorkWave transfer request
Salesforce Sales Cloud gotchas
Workflow Rules and Process Builder are retired
Bulk API batch quota exhaustion during large imports
Storage overage billing is non-obvious
Account-Contact many-to-many relationship mapping
Territory and team member import ordering dependencies
Pair-specific challenges
Migration approach
Stand up Salesforce custom objects and field schema first
Before any data moves, your Salesforce admin (or our team) creates the custom objects needed for this migration: Property__c, Equipment__c, Route__c, RouteStop__c, Invoice__c, InvoiceLine__c, Payment__c, and any custom fields on Account and Case for RealGreen-specific data like FlagCodes__c, Lawn_Size_Sq_Ft__c, and Origin_Work_Order_ID__c. We deliver a complete schema setup plan based on your RealGreen configuration inventory so the Salesforce side is ready before validation runs. Record Types and page layouts for Case are also configured at this stage.
Resolve employees to Salesforce users by email match
RealGreen employee records are matched to Salesforce Users by email address. Active field technicians receive Platform or Field Service licenses; office staff receive Sales Cloud licenses. Unmatched employees are flagged before migration — your team either invites them to Salesforce first or assigns their records to a fallback owner. No record lands in Salesforce without a resolved OwnerId. This step also captures the employee-to-user mapping needed to resolve Route__c.Assigned_Crew__c lookups.
Migrate accounts and contacts before cases and custom objects
Salesforce requires AccountId on Contact records and WhatId/WhoId lookups on Case and Task records. We sequence the migration so foreign keys resolve correctly: Accounts first, then Contacts with role assignments, then custom Property__c and Equipment__c records, then Work Orders → Cases with status mapping, then Routes → Route__c and RouteStop__c with sequence preservation, then Invoice and Payment history. This ordering ensures referential integrity — cases link to accounts, route stops link to accounts and routes, payments link to invoices and accounts.
Run a sample migration with field-level diff before full commit
A representative slice migrates first — typically 100–500 records spanning accounts, contacts, work orders, routes, and a few invoices. We generate a field-level diff between the RealGreen source and the Salesforce destination so you can verify work order status mapping, property field population, equipment linkage, route stop sequencing, and invoice/payment preservation before the full run commits. This is the checkpoint where you approve or adjust the mapping plan.
Execute full migration with delta-pickup window for in-flight records
The full migration runs against Salesforce using Bulk API for high-volume objects (Accounts, Contacts, Cases) and REST API for custom objects with complex field sets. A delta-pickup window — typically 24–48 hours — captures any records created or modified in RealGreen during the cutover so Salesforce reflects the final operational state at go-live. FlitStack AI uses scoped read access on RealGreen; your team keeps working in Service Assistant 5 throughout. An audit log captures every operation, and one-click rollback is available if post-migration reconciliation reveals data quality issues.
Platform deep dives
RealGreen by WorkWave
Source
Strengths
Weaknesses
Salesforce Sales Cloud
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across RealGreen by WorkWave and Salesforce Sales Cloud.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
RealGreen by WorkWave: Not publicly documented — access negotiated with WorkWave API Sales.
Data volume sensitivity
RealGreen by WorkWave doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during RealGreen by WorkWave to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.
Walk through your RealGreen by WorkWave to Salesforce Sales Cloud migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave RealGreen by WorkWave
Other ways to arrive at Salesforce Sales Cloud
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.