Migrate from ForceManager CRM to Nutshell

ForceManager Company records map to Nutshell Company. The company name, type, rating, address, and responsible user migrate directly. Any z_-prefixed extra fields on Company are parsed from the Fields endpoint, stripped of the prefix, and recreated as native Nutshell custom properties. Owner assignment resolves by matching ForceManager user email to Nutshell User email.

ForceManager Contact records map to Nutshell Person. Name, email, phone, title, and address fields migrate directly. Contact-to-Company associations are preserved via the Company lookup relationship in Nutshell. Z_-prefixed extra fields are mapped to native Nutshell Person custom fields with the prefix removed and the label set to the human-readable name retrieved from the Fields endpoint.

ForceManager Opportunity maps to Nutshell Deal. Stage name, monetary value, responsible user, expected close date, and linked Company and Contact references transfer directly. Custom opportunity fields (z_-prefixed) are mapped to Nutshell Deal custom properties. Pipeline stage order is recreated as a Nutshell pipeline with stages mapped by sequence.

ForceManager Activities represent logged calls, meetings, and field interactions. We map activity type, date, duration, and linked Contact and Company to Nutshell Activity entries on the Person and Company timeline. GPS coordinates stored on ForceManager Activities are flagged as a metadata field because Nutshell does not have a native map or GPS anchor; coordinates are preserved in a note field for reference. Activity history is replayed as a chronological sequence of entries against the linked Person or Company record.

ForceManager Events are calendar-level entries with start/end time, location (including GPS), and attendees. These map to Nutshell Activity entries of type Meeting with the date, duration, and location fields populated. Attendee associations are mapped as linked Person records. GPS coordinates from ForceManager Event location are retained in a location note field.

ForceManager Tasks map to Nutshell Tasks. Status (open/completed), due date, title, description, and assignee migrate directly. Owner resolution uses email-based matching against Nutshell Users. Completed tasks retain their completion timestamp; open tasks show as pending in Nutshell.

ForceManager Sales Order and Sales Order Line records exist in the API but represent a transactional layer that Nutshell does not natively model as a standalone object. We map Sales Order header fields (order number, date, total) to custom properties on the linked Nutshell Deal. Line items are mapped as a custom multi-value field or JSON-embedded property on the Deal record. If the customer requires full order history, we recommend a separate order management tool and note this in the scoping report.

ForceManager Users are extracted via the /users endpoint and matched by email address to Nutshell User accounts. Owner assignments on Companies, Contacts, and Opportunities reference ForceManager user IDs; we resolve these to Nutshell User IDs at migration time. Any ForceManager user without an active Nutshell account is placed in a reconciliation queue for the customer's admin to provision before record import proceeds.

All ForceManager custom fields carry a z_ prefix in the API payload. We query the Fields endpoint during extraction to capture the label and field type for each z_-prefixed field, then create native Nutshell custom properties with human-readable labels. Field types are mapped: text to Nutshell Text, date to Date, number to Number, and picklist to Dropdown. Custom fields on Companies, Contacts, and Opportunities are handled per-entity.