Migrate from Demandforce to Odoo CRM

Demandforce appointment confirmation status has no native Odoo CRM equivalent

Demandforce tracks whether an appointment is confirmed, cancelled, or marked as a no-show — a field that sits at the intersection of scheduling and pipeline health. Odoo CRM's activity model (crm.activity) records the date and type of an activity but does not have a native confirmation-state field. FlitStack creates a custom Char field x_confirmation_status on crm.activity records during migration so you can filter by confirmation state in Odoo's kanban and list views. Without this custom field, cancelled and no-show appointments would be indistinguishable from completed activities, which breaks recall and reporting logic that depends on distinguishing attended from missed appointments.

Demandforce's two-way SMS threads require a third-party SMS gateway in Odoo

Demandforce's primary differentiator for healthcare practices is HIPAA-compliant two-way text messaging integrated directly into the patient record. Odoo CRM in its Community edition has no built-in SMS sending capability — it can store inbound messages as mail.message records linked to res.partner, but it cannot send SMS without a third-party SMS gateway module (such as a Twilio or Vonage integration from the Odoo Apps Store). FlitStack migrates the text message history as read-only mail.message records, but the ability to send outbound SMS from Odoo requires your team to install and configure an SMS gateway app after go-live. We document the gateway selection options and configuration steps as part of the post-migration handoff.

Demandforce recall reminders need Odoo Automated Actions to replace Demandforce workflows

Demandforce's recall feature automatically sends patients reminders when their next-appointment due date passes — a critical patient retention mechanism for dental and medical practices. In Odoo CRM, this logic must be rebuilt using Automated Actions (ir.cron jobs triggering server actions on crm.lead records where x_next_recall_date equals current_date). FlitStack extracts the recall-interval rules from Demandforce (e.g., '6 months after a cleaning appointment') as structured JSON, but the Automated Action configuration requires your Odoo developer or consultant to implement. We include a step-by-step rebuild guide as part of the migration deliverables.

Demandforce multi-location structure requires Odoo company setup or location-field strategy

Many Demandforce customers run multi-location practices — each location may have its own practitioner roster, business hours, and patient lists. Odoo handles multi-location data in one of two ways: as separate res.company records (which creates isolated data per company and requires the Odoo Studio multi-company rules to be configured), or as a single company with an x_practice_location Char field on res.partner for filtering. FlitStack surfaces the current location assignments during the sample migration so your team can choose the appropriate Odoo configuration before the full run. Mis-configuring this choice can result in cross-location data leakage or over-separation that fragments your CRM view.

Demandforce reputation and listing data does not migrate to any Odoo object

Demandforce's listing management module maintains presence across 150+ directories (Google Business Profile, Healthgrades, Vitals, etc.) with automated claim-and-publish workflows. Odoo has no native directory-listing management capability — even the Odoo Website app handles only the company's own website listings, not third-party directory citations. FlitStack exports the Demandforce listing data (directory URLs, claim status, review request history) as a structured JSON report. Your team retains this data for manual re-entry into a dedicated reputation tool (such as Birdeye, Podium, or SOCi) post-migration. This is a business-process gap, not a technical data-loss issue, but it requires advance planning.