Migrate from RAMM to Nutshell

RMM client organizations map directly to Nutshell Companies. Organization name becomes Company Name. Domain and address fields map to their Nutshell equivalents. If your RMM uses parent-child organization hierarchies, the parent organization becomes the primary Company and child organizations require disambiguation — either as separate Nutshell Companies or as a custom field for relationship context.

The primary contact associated with an RMM client organization becomes a Nutshell Person record linked to the corresponding Company. Name, email, phone, and title fields map directly. Nutshell People can link to multiple Companies, which handles scenarios where a single contact manages multiple client organizations in your RMM platform.

RMM platforms may store multiple contacts per client organization (technical contacts, billing contacts, executives). We create a separate Nutshell Person for each unique contact email and link all to the same Company. Duplicate email addresses are flagged for manual resolution before migration.

RMM device records (workstations, servers, network devices) do not have a direct Nutshell equivalent. We preserve device summary data — device type counts, last check-in date, warranty status — as custom fields on the Nutshell Company record. Detailed device inventory requires a separate asset management tool or a Nutshell custom object.

RMM support tickets map to Nutshell Tasks. Ticket subject becomes Task name. Ticket description and internal notes merge into the Task's notes field. Ticket status (open, pending, resolved) maps to Nutshell Task status. Open tickets retain their status; closed tickets migrate as completed Tasks with original close date preserved.

Ticket comment threads from the RMM platform become Nutshell Notes attached to the corresponding Task. Original comment timestamps, author names, and message bodies are preserved in each Note, including any inline formatting or file references. This approach maintains the full support conversation history within Nutshell for review by the sales team.

RMM service contract details (contract name, tier, renewal date, monthly/annual billing) become custom fields on the Nutshell Company. Contract value and billing frequency map to number and text fields respectively. Contract renewal dates set as reminder dates in Nutshell's built-in task scheduling.

RMM technician accounts are matched to Nutshell users by email address. If a technician email does not match an existing Nutshell user, the record is assigned to a designated fallback owner (configurable by your team) and flagged in the pre-migration report for user creation before go-live.

RMM ticket attachments such as screenshots, log files, and exported documents are re-uploaded to Nutshell Notes as file attachments on the associated Task record. Nutshell enforces file size limits per plan; any attachment exceeding the threshold is flagged during the audit and stored externally, with a URL reference inserted into the Note. This ensures all relevant support files remain accessible within Nutshell while respecting storage constraints.

Client and contact tags from the RMM platform transfer as Nutshell Tags, preserving the original labeling hierarchy. Tags that were applied to organizations attach to the corresponding Nutshell Company record, while tags assigned to contacts attach to the associated Person record. This migration of tags keeps your categorization logic intact, enabling consistent filtering and reporting in Nutshell.