Migrate from OneSuite to Nutshell

OneSuite Clients with type 'person' map to Nutshell Contact. Clients with type 'company' or those with a business name field populated map to Nutshell Account with the company name as Account Name. Clients flagged as both (person at a company) get an Account created first, then a Contact attached to that Account with the company association preserved in the AccountId field.

OneSuite Leads map directly to Nutshell Leads with stage, source attribution, and any scoring values preserved. The OneSuite lead status property maps to Nutshell's Lead Status field. If the account approached or hit the 10,000-lead cap during scoping, we pre-verify the count before migration to avoid silent truncation that OneSuite's UI does not warn about.

Nutshell has no native project entity, so OneSuite Projects do not map to a first-class object. We extract project name, description, milestones (as a bulleted Note body), and tasks (as separate Note records or as a structured list on the linked Client Account), then attach all resulting notes to the Client Account or Contact that owns the project. The customer's admin rebuilds project tracking in Nutshell using Tasks and the Activity timeline.

OneSuite Invoices have no native Nutshell equivalent. We extract invoice metadata (invoice number, amount, status, client name, date, line items as a text summary) and attach it as a Note on the related Client Account or Contact. We flag multi-currency or custom tax configurations that require manual reconciliation in the destination system. Customers using Nutshell's Quotes & Invoices add-on ($67/company/month) may rebuild invoices from the extracted metadata.

OneSuite Document metadata (name, type, associated Client or Project, URL) migrates as a Note attached to the linked Account or Contact. Binary file content does not migrate because Nutshell has no native document management layer beyond attachments. We pre-scan total file volume against the source plan's storage tier (30 GB Freelancer, 60 GB Growing Agency) and flag any account exceeding its cap before migration so the customer can address storage before records move.

OneSuite Members map to Nutshell Users. We match by email address. Any Member without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import continues, because OwnerId references must be valid at the time of record insert.

OneSuite custom fields are flattened directly onto entities with slug keys (e.g., client-tier appears as clientTier on the record). We parse the API response and remap each slug to the destination Nutshell custom field name, preserving all values. If Nutshell does not yet have the equivalent custom field configured, we flag it for creation before migration runs to avoid silent value drops.

OneSuite Lead pipeline stages map to Nutshell Lead Status values. We preserve stage names and order. Any stages with custom automation or scoring rules are flagged in the handoff document because Nutshell's workflow model differs from OneSuite's automation triggers.