Migrate from openCRX to Nutshell

openCRX Contact (individual account subclass) maps to Nutshell Person. We extract first name, last name, email, phone, postal address, and any assigned user from the Contact object. openCRX's extensive Contact attribute set (notes, ratings, user-defined features) is mapped to Nutshell standard fields and custom fields where the type is supported. openCRX segment assignments are not carried; Nutshell uses a flat user-assignment model instead.

openCRX LegalEntity (organisation account subclass) maps to Nutshell Company. Company name, website, industry, and address fields migrate directly. The openCRX postal address and phone number complex objects map to Nutshell's address and phone fields. openCRX's multi-address support (billing, shipping, office) collapses to a single Nutshell Company address; secondary addresses are documented as note text.

openCRX Opportunities inherit from abstract contract classes and map directly to Nutshell Deals. The openCRX opportunity rating, estimated value, probability, expected close date, and assigned owner migrate as standard Nutshell Deal fields. openCRX stage values map to Nutshell pipeline stages, with a custom text field capturing the original openCRX contract status for audit. Parent Account lookup resolves at migration time via the LegalEntity-to-Company mapping.

openCRX Quotes inherit from the same contract hierarchy as Opportunities and map to Nutshell Deals with a custom field capturing original quote metadata (quote number, validity period, and line items as structured text). Quote line items from openCRX contract positions are appended as a formatted note block on the target Nutshell Deal. This approach preserves full quote detail without creating a separate Quote object, which Nutshell does not expose as a standard API object.

openCRX Sales Orders inherit from the contract hierarchy and map to Nutshell Deals using the same collapsing strategy as Quotes. Order number, status, shipping address, and order line items are captured as structured text in a custom field on the target Deal. openCRX's order-to-quote transformation logic (which converts a Quote to a Sales Order in openCRX) is documented as a note in the migration handoff so that Nutshell admins can manually reproduce the workflow if needed.

openCRX Invoices are terminal contract objects in the sales process chain and map to Nutshell Deals using the same collapsing approach. Invoice number, date, payment terms, and line items are captured in a custom field on the Deal. openCRX's invoice payment status and billing address migrate as structured note text. Customers needing separate invoice records in Nutshell use an AppExchange partner app or manage invoicing in a dedicated accounting tool post-migration.

openCRX Products map to Nutshell Products with name, SKU (product code), and description migrating directly. Multi-currency price lists from openCRX collapse to a single USD price in Nutshell (or the customer's chosen base currency); the original multi-currency price context is preserved as a text note on the Product. openCRX bundle products and design-to-order configurations are documented as a product structure note.

openCRX Activities with rich attributes (time tracking, activity trackers, custom feature definitions) map to Nutshell Activities. Call, email, meeting, and task subtypes are preserved through Nutshell's activity type field. openCRX Activity Tracker grouping is documented as note text on the parent Contact or Deal in Nutshell. We set Activity timestamps to the original openCRX created date to preserve the historical timeline ordering.

openCRX custom fields added via DataBinding PropertySet are feature definitions stored in the UI customising layer and bound to CrxObject at runtime. We identify all active custom fields during scoping, map their openCRX attribute types to Nutshell custom field types (Text, Number, Date, Currency, Picklist, Boolean), and create corresponding Nutshell custom fields on the appropriate object before migration. openCRX attributes that use unsupported Nutshell field types migrate as Text. The full custom field inventory is included in the migration handoff document.

openCRX binary attachments linked to Contacts, Accounts, or Opportunities are extracted from the storage layer (WebDAV-accessible on Linux or macOS export clients) and re-attached to the corresponding migrated Nutshell records via Nutshell's attachment API. We verify attachment accessibility during scoping since WebDAV exports on Windows can silently fail due to Microsoft's WebDAV client quirks documented in openCRX's groupware services guide. Any attachments that cannot be accessed through a compatible client are listed in the handoff with a note on the export method required.