Migrate from Weave to Nutshell

Weave patients map directly to Nutshell People. The primary name, email, phone, and address fields translate field-for-field. Weave patient status (active/inactive) maps to Nutshell's People status field. Original create timestamps are preserved in a custom field since Nutshell's Created Date reflects the migration run.

Weave business records map to Nutshell Companies. Business name, address, website, and industry classification translate directly. Multi-location businesses from Weave collapse to one Company record in Nutshell, with additional addresses preserved in a custom field. All business contact information carries over unchanged during the migration run.

Weave appointments have no direct Nutshell equivalent. Appointment dates, types (cleaning, consultation, procedure), and confirmation status migrate as custom date and pick-list fields on the Person record. The appointment type field uses a value map to match Weave's taxonomy to Nutshell pick-list options. Multi-appointment history requires custom field setup before migration.

Weave call records (incoming, outgoing, missed) become Nutshell Tasks with Type='Call'. The task subject contains the call direction and duration. Original timestamps are preserved. Nutshell Tasks appear on the Person's activity timeline, maintaining the relationship context even without Weave's call threading.

Weave text message threads become Nutshell Tasks with Type='Note' and a custom field indicating SMS. The task body contains a truncated transcript for reference. Full thread history is preserved in a linked attachment if available from Weave export. Nutshell does not support SMS threading natively.

Weave payment history (amounts, dates, status) migrates as custom fields on the Person record. Weave's Text-to-Pay transactions become a custom field tracking last payment amount and date. Nutshell has no native payment object, so outstanding balances and payment plans are preserved as custom fields for billing reference.

Weave's integrated review request system and associated patient review status have no Nutshell equivalent. Review request history migrates as a custom field tracking whether a review was requested and the outcome (requested, submitted, pending). Actual review content and review platform links are not migratable and should be archived separately if required for reference.

Weave recall entries (follow-up appointments due) become Nutshell Tasks with a due date. The task subject indicates recall type (6-month cleaning, annual exam). Completed recalls map to a 'Completed' task status. This preserves the recall workflow logic for manual rebuild in Nutshell.

Weave custom fields on patient records require Nutshell custom field creation before migration. Common healthcare fields like insurance carrier, referral source, treatment plan type, and preferred provider map to Nutshell pick-list or text fields. Field type translation is required since Weave and Nutshell use different type taxonomies.

Weave user accounts are matched to Nutshell users by email address during migration. Any Weave user without a corresponding Nutshell account gets flagged before migration begins, requiring admin resolution. Weave role and permission assignments do not translate directly to Nutshell's permission model and must be reconfigured by your admin post-migration.

Weave digital forms and patient intake data have no Nutshell equivalent in the standard CRM model. Completed form submissions and their data are not migratable through the API. If compliance or historical reference requires retention, this content should be exported separately as PDF archives before the cutover date.

Weave file attachments including patient documents, signed forms, and uploaded records re-upload to Nutshell as attachments on the Person record. File size limits apply per Nutshell's attachment constraints. Inline images extracted from Weave communications download separately and rehost as distinct attachments in Nutshell.