Migrate from RealGreen by WorkWave to Nutshell

RealGreen's customer record maps directly to Nutshell Person — the primary contact at a service address. The customer name, phone, email, and all standard contact fields migrate directly. If the customer has multiple service locations, the primary address becomes the Person address; secondary locations are preserved as custom fields.

RealGreen customers who have not yet been converted to active service accounts are treated as Leads in Nutshell. Any customer record with a 'Lead' or 'Prospect' status in RealGreen's flag-code system routes to Nutshell Lead. Active service customers map to Nutshell Person and are linked to the corresponding Company account.

RealGreen supports multi-location and multi-branch configurations. Each branch or operating entity in RealGreen becomes a separate Nutshell Company record. Nutshell's Teams feature can be used to isolate branch-level data visibility if your migration requires it. If your RealGreen setup uses parent-child branch relationships, those hierarchies are flattened during migration — each branch becomes an independent Company, and parent-child relationships are stored as custom fields for reference.

RealGreen Programs (recurring service agreements like 'Weekly Lawn Care' or 'Monthly Landscaping') have no direct Nutshell equivalent. We map each Program to a Nutshell Deal with the program name as the Deal name, the service type as a custom field, and the program status (Active, Paused, Cancelled) mapped to Nutshell's pipeline stage values via value_mapping.

Work Orders represent individual service visits and do not exist in Nutshell. We migrate Work Order metadata (service date, crew assigned, services rendered, status) as a structured note on the associated Nutshell Deal and as custom date fields where Nutshell's schema allows. Work order totals can be summed and stored on the parent Deal as a custom monetary field.

RealGreen Invoices map to Nutshell Activity records attached to the relevant Deal. The invoice number, total amount, status (Paid, Outstanding, Overdue), and payment method are stored as custom fields on the Activity. Nutshell does not have a native billing module; invoice records are preserved for historical reference.

Payments made against RealGreen invoices migrate as Nutshell Activities with type='Payment'. The payment date, amount, and method are captured in custom fields. Nutshell's activity timeline provides a payment history view per Deal. Multiple payments on the same invoice are aggregated in the activity sequence, and partial payments are recorded individually so your team can track payment progress without accessing RealGreen directly.

RealGreen's property-inventory records (equipment on-site, property size, access notes) have no Nutshell equivalent. We create custom fields on the Person record (property notes, equipment list) and on the Company record (property count, average lot size) to preserve this data. For bulk property data, we store a structured text block on the Company.

RealGreen's custom properties on Customer, Program, or Work Order objects (e.g., 'Preferred mowing height', 'Irrigation zone count', 'Customer tier') become Nutshell custom fields. We create them on the appropriate Nutshell object (Person, Company, or Deal) before migration so the field mapping can reference them.

RealGreen's flag codes (e.g., 'Do not mow', 'Key on file', 'Gate code') drive workflow decisions. In Nutshell, these become custom pick-list fields on the Person record. We map each flag code value to a corresponding pick-list option and preserve the original flag descriptions in the field's help text.

RealGreen users and crew owners are resolved by email match against Nutshell users. Any RealGreen owner without a matching Nutshell user email is flagged before migration and can either be invited to Nutshell or assigned to a fallback Nutshell user. Crew assignments on Work Orders are preserved as text in the Work Order note.

RealGreen file attachments (photos, signed forms, proposals) cannot be migrated directly to Nutshell's activity notes. We export attachments to a structured ZIP archive and provide a reference URL list on the corresponding Nutshell record. Nutshell's attachment capability is limited to inline files on Notes; full document management requires a separate DMS.