Switching From NinjaOne? Import Clients, Custom Fields and Warranty Dates

What's in the demo

• Organizations → Bulk import with ninjaone-organizations.csv: Breeze maps the columns by header (Organization, Location as Site, ID as External ID, System, Timezone)
• Preview of 6 rows: Bayview Pediatrics (Main Clinic, Westside Clinic, ID 1187) shows Already linked; Granite Peak Engineering, Lakeview Family Law and Copper Ridge Veterinary show New. Existing organizations set to Skip, then Import 6 selected → "4 imported, 2 skipped."
• Devices & Assets for Bayview Pediatrics: 8 devices already enrolled, and Add → Install agent…
• Import from another RMM, source NinjaOne, ninjaone-custom-fields.csv: 3 fields found, Purchase date set to date and Clinical workstation to boolean
• This organization only, then Preview: backupplan, purchasedate and clinicalpc all "Will be created" → Create fields
• Step 2 with ninjaone-devices.csv: id → Source device ID, systemName → Hostname, serialNumber → Serial number
• backupPlan, purchaseDate and clinicalPc → Custom field with their keys, warrantyEndDate → Warranty end date, date format MM/DD/YYYY, Preview 8 rows
• 6 rows Matched, BVP-LAB-01 Not found (no agent yet), BVP-NURSE-01 Ambiguous with 2 candidates; pick one and tick the row
• Import 7 rows → "Applied 28, skipped 0, failed 0 values". Preview again and every row reads Linked, values Already set
• Device list → Columns → Backup plan and Clinical workstation: BVP-SRV-01 "Nightly image", BVP-EXAM-01 "Yes"

Questions this video answers

Can I migrate devices from NinjaOne or another RMM into Breeze RMM?

Not as records. A device appears in Breeze when the Breeze agent enrolls on it (Devices & Assets → Add → Install agent…). The usual path is to push the installer with your old RMM's script engine, keep the old agent until every machine shows up in Breeze, then remove it. What the importer carries over is the data about those devices: custom field values and warranty end dates.

How do I import my client list into Breeze RMM?

Organizations → Bulk import. Upload a CSV with organization (required), site, external ID, external system and timezone. Breeze maps columns by header, previews each row (New, Already linked or a name match), and keeps the external ID so running the file again doesn't create duplicates.

How do I bring custom fields over from my old RMM?

Devices & Assets → Import from another RMM. Step 1 reads the old RMM's field list (sources: Datto RMM, NinjaOne, ConnectWise Automate, N-central or Generic CSV) and creates the fields, as text unless you set a type. Step 2 reads a device export and writes the values to enrolled devices. Files are CSV; there is no API connector.

Can Breeze RMM import warranty dates?

Yes. In step 2, map the column to Warranty end date and it lands in Breeze's own warranty record, which feeds warranty alerts. Set the date format to match the export (MM/DD/YYYY for US dates).

What if a device in the export isn't in Breeze yet?

Its row shows Not found and nothing is written, so it becomes your list of machines still missing the agent. Ambiguous rows wait for you to pick a device. Imported rows stay linked to their source device ID, so you can re-run the same file later; values already set are left alone unless you choose Overwrite it.