Migrate from NeoDeck Holdings to Nutshell

Clinical encounter records have no native Nutshell object — they become Notes or Tasks

NeoDeck encounter records (office visits, telemedicine sessions, lab visits) carry clinical context that Nutshell cannot represent structurally. There is no Nutshell equivalent of a clinical encounter object — appointments and visits cannot map to a native entity. FlitStack converts each NeoDeck encounter into a Nutshell Note attached to the corresponding Person record, with encounter date, type, and provider embedded in the note body. High-urgency or flagged encounters are converted to Nutshell Tasks with the patient as the related Person. This means encounter history is searchable in Nutshell as Notes but does not appear in Nutshell's standard Activity timeline views designed for sales activities.

Nutshell Deals do not support custom fields — clinical claim data must attach to Person records

Nutshell's Deal object does not support custom fields, which constrains how insurance claim data from NeoDeck can be stored. NeoDeck insurance claims (with claim number, amount, status, and payer) map to Nutshell Deals for pipeline tracking, but payer names, insurance policy numbers, and authorization codes cannot be stored on the Deal itself. FlitStack resolves this by storing payer names on the related Person record (Insurance_Payer__c) and keeping claim-level metadata in the Deal name and stage. If your team needs claim-level detail visible on the Deal record, that information must be surfaced via a linked Note or managed outside Nutshell in a spreadsheet export.

NeoDeck API access is not publicly documented — export path determines migration timeline

NeoDeck Holdings provides no publicly documented REST API for programmatic data extraction. The platform is a web application backed by a database; data access requires either a structured export from within the application (if the export feature is enabled for your account), a direct database query (if you have DB credentials and your contract permits access), or screen-scraping of exported reports. FlitStack begins every engagement with a scoping call to identify the available export path and any contractual constraints on data extraction. The chosen export method is the primary variable that determines scoping hours and whether the migration qualifies for the standard timeline or requires extended planning.

Patient consent and HIPAA obligations are not handled by the migration tool

NeoDeck Holdings stores protected health information (PHI) subject to HIPAA. Nutshell is a general-purpose CRM with no HIPAA-specific controls, business associate agreements, or audit logging for PHI access. Migrating patient records (names, DOB, diagnoses, allergies, insurance information) from NeoDeck to Nutshell transfers data from a HIPAA-regulated environment to a standard commercial CRM. Your organization is responsible for determining whether this transfer is permissible under your HIPAA compliance program, including obtaining any required patient authorizations and executing a business associate agreement if Nutshell will receive PHI. FlitStack can migrate the data but does not provide HIPAA compliance advisory services.

Prescription and lab result data maps to freeform text fields with no structured retrieval

NeoDeck stores prescription details (medication name, dosage, frequency, prescriber, pharmacy) and lab results (test name, result value, reference range, units) as structured clinical fields. Nutshell has no native field types for medication lists or lab result sets — these must be stored as custom text fields on the Person record. There is no way to retrieve individual prescriptions or lab values as separate records in Nutshell; they are concatenated into a single text value. This means a provider looking for a specific historical medication in Nutshell must search within a text block rather than query a structured field. FlitStack preserves the data completely but cannot create structured retrieval for fields that Nutshell does not support.