Migrate from Demandforce to Nutshell

Demandforce people (patients or clients) map directly to Nutshell People. Core fields — name, email address, phone number, and mailing address — transfer as-is. Demandforce owner assignments (the staff member linked to each contact) map to Nutshell's 'assigned_to' user field via email-match resolution. Unmatched owners are flagged before the migration commits.

Demandforce companies (practice names and business entities) map to Nutshell Companies. Company name, website domain, physical address, and industry classification transfer as direct field mappings. For multi-location Demandforce accounts, each location becomes a separate Nutshell Company — FlitStack AI preserves location-specific address and contact data per record.

Demandforce appointment records have no direct Nutshell equivalent. Each appointment converts to a Nutshell Task with the original appointment date and time preserved as the task due date, the appointment status (confirmed, cancelled, no-show) stored in a custom 'Appointment_Status__c' field, and the Demandforce appointment type stored as a custom 'Appointment_Type__c' field. The linking person (patient) is associated via Nutshell's person-task relationship.

Demandforce email logs — outbound marketing emails, confirmation emails, and recall reminders — are stored as Communication records with timestamps and content. These migrate as Nutshell Emails linked to the corresponding Person record, with the original send date preserved and the email subject line carried forward. Email body content migrates as a note attachment.

Demandforce two-way text messages migrate as Nutshell Tasks with a custom 'Communication_Type__c' field set to 'SMS'. The original message content, direction (inbound/outbound), and timestamp transfer. Because Nutshell's Engagement SMS product is a separate add-on, the text content is preserved as activity history but will not be visible inside Nutshell's native SMS interface without the Engagement add-on.

Demandforce's automated review-request workflow generates review invitation records with statuses (sent, opened, reviewed). Nutshell has no native review-request object. Review request history migrates as a Note on the Person record containing the original review request date, status, and platform (Google, Facebook, etc.) — stored for historical reference but not re-triggered in Nutshell.

Demandforce email campaigns (templates, send dates, audience lists) have no Nutshell equivalent. Campaign metadata — campaign name, subject line, send date, and recipient count — migrates as a Note on the associated Company record. Individual campaign member records do not transfer because Nutshell does not have a campaign membership model. The campaign audience list itself must be rebuilt using Nutshell Marketing's audience segmentation.

Demandforce custom fields on Person records — such as patient account numbers, treatment histories, or recall dates — require manual re-creation in Nutshell's custom field editor (Settings > People > Custom Fields). FlitStack AI generates a field-mapping manifest listing every Demandforce custom field, its data type, and its current value distribution so Nutshell admins can create matching fields before or after the migration.

Demandforce custom fields on Company records — such as multi-location groupings, practice type, or recall scheduling preferences — are documented in the mapping manifest. These must be created manually in Nutshell's Settings > Companies > Custom Fields. FlitStack AI provides the complete list with pick-list values and data types so the Nutshell admin can pre-build the schema.

Demandforce staff members (owners assigned to contacts, appointments, and campaigns) are matched to Nutshell users by email address. Unmatched Demandforce owners — staff who will not have Nutshell accounts — are reassigned to a designated fallback user before migration. Owner resolution is validated in the sample migration phase so no contact lands without a valid Nutshell user assignment.

Demandforce uses tags to categorize contacts (e.g., 'recall-due', 'high-value-patient', 'referral-source'). Tags migrate as Nutshell Tags on the Person record. Tag names transfer as-is. Because Nutshell tags are free-form labels (not pick-list controlled), there is no value-mapping required — the full tag vocabulary migrates.

Demandforce records people in a pre-appointment state — those who requested an appointment but have not yet been seen — as leads. These map to Nutshell Leads with the original inquiry date and communication channel preserved. Leads that convert to appointments in Demandforce will have both a Lead record and an Appointment record; the migration links both to the corresponding Nutshell Person.