Migrate your N-able MSP Manager data

Customer records are the primary organizational unit in MSP Manager, holding locations, program levels, and billing info. The OData export exposes full customer records including address, tax rate, and business hours. We preserve all standard fields 1:1 during migration.

Contact records link to Customer objects and include name, email, phone, and role. RMM sync can auto-create contacts from N-able N-sight. We map contacts to the destination's equivalent contact or person object.

Tickets are the core operational record, tied to a Customer and optionally to a Customer Contact. Standard fields include status, priority, category, assigned technician, and timestamps. We migrate open and recently closed tickets by default and flag archival tickets for scoping conversation.

MSP Manager supports user-defined custom fields on tickets (text, number, dropdown, date). Documentation is sparse and some helpdesk pages return 404. We inspect the account schema via API before migration and build a field map to the destination, flagging any unsupported field types for manual review.

Time logged against tickets captures billable hours with technician, date, duration, and optional description. Batch invoice generation reads from these entries. We migrate time entries as a child of their parent ticket record, preserving the link where the destination supports hierarchical ticket-line items.

Expense records attach to tickets or stand alone and include amount, date, vendor, and description. Mapping depends on whether the destination supports expense objects or bundles them into line items. We ask customers to confirm their expense tracking workflow during scoping.

MSP Manager generates invoices from billable time and expenses. Invoices carry status (draft, sent, paid). We migrate invoice headers and line items, but paid/unpaid status sync depends on the destination's accounting integration capabilities.

KB articles live under Customers and contain procedure and policy documentation for end clients. Not all destinations have a matching KB object; where absent, we export KB content as a structured document bundle or map it to the destination's help center articles.

Assets track devices associated with a Customer, including hardware specs and status. Asset data is partially managed by the N-sight RMM sync. We migrate the asset record but note that full device details may live in N-able N-sight rather than MSP Manager itself.

Portal settings include branding (logo, colors) and ticket submission preferences per customer. We capture configuration data but cannot guarantee pixel-perfect portal reproduction in a different PSA; we treat portal settings as informational metadata for manual reconfiguration.

Service items define the scope and pricing of managed services per customer (e.g., per-user or per-device plans). These tie into billing workflows. We preserve service item names, pricing, and billing model type and map them to the destination's equivalent recurring billing or agreement objects.

User accounts with role-based permissions (Admin, Technician, View-only) control access across all MSP Manager objects. We migrate user records and map roles to the destination's permission model, noting that role semantics may differ between platforms.