Migrate from My Practice Now to Odoo CRM

My Practice Now client records map directly to Odoo res.partner. The partner serves as the unified contact and company record. Address fields, phone, email, and custom client properties transfer as fields on res.partner. Multiple My Practice Now clients sharing one email are flagged for deduplication before migration.

Each My Practice Now appointment becomes a crm.lead entry. The appointment date maps to crm.lead create_date, the practitioner maps to user_id, and the appointment type or status maps to stage_id. Notes from the appointment session transfer to the lead description or a custom field on crm.lead for continuity.

My Practice Now invoices map to Odoo account.move records with move_type='out_invoice'. Line items map to account.move.line entries with product_id, quantity, and price_unit. Partner_id links to the migrated res.partner record. Fiscal position mapping applies if My Practice Now stores tax information.

My Practice Now practitioner accounts are matched to Odoo res.users by email address before migration begins. If a practitioner's email does not correspond to an existing Odoo user, FlitStack flags that practitioner and either reassigns their appointments to a designated fallback Odoo user or temporarily holds those appointments pending creation of the missing user accounts in Odoo.

My Practice Now custom client properties (treatment notes, insurance group, referral source) require custom fields on res.partner in Odoo. Field types are created to match source types. Values are loaded after the custom field definition exists in the Odoo database.

My Practice Now service items are mapped to product.product records with type set to 'service'. Each product.product record is then referenced in account.move.line entries to represent the line items on invoices. If My Practice Now includes a price list, FlitStack translates it into Odoo's pricelist model, associating the appropriate pricing rules with the migrated products and customers.

Client notes and session history from My Practice Now are imported as Odoo mail.message records linked to the corresponding res.partner, preserving the original creation timestamp and the practitioner who authored each note. If the notes contain file attachments, FlitStack stores them as ir.attachment records associated with the partner or lead, ensuring the original files remain accessible within Odoo's document management system.

Appointment reminder rules defined in My Practice Now have no direct equivalent within the Odoo CRM data model, because Odoo handles reminders through its calendar module rather than as CRM attributes. FlitStack exports the complete reminder configuration—including notification timing, channels, and recipient logic—as a structured reference document that your Odoo administrator can use to recreate the rules manually in Odoo calendar and mail.activity, preserving the same reminder behavior after migration.

Tax identification numbers and billing preferences stored in My Practice Now are mapped to Odoo res.partner fields such as vat and property_payment_term_id, while any tax region mappings are represented as account.fiscal.position records. This configuration-level data is loaded during the migration alongside the actual record data, ensuring that fiscal and payment term settings are applied automatically to the migrated partners and invoices in Odoo.

My Practice Now report definitions and dashboard configurations do not migrate because they are platform‑specific UI constructs with no direct Odoo equivalent. The underlying data—client records, appointments, and invoices—is fully present in Odoo and can be queried using Odoo's built‑in reporting tools, pivot views, or custom SQL views built against the migrated tables. Your team will need to rebuild any custom reports and dashboards in Odoo using Studio or SQL‑based reporting.