Migrate from MOGO to monday CRM

Monday CRM has no native appointment or scheduling object — all scheduling must be constructed from board Items and Date columns

MOGO's appointment model (date, time, provider, procedure, status, patient link) has a direct structural equivalent in Monday CRM only if you build a Scheduling board with a Date column, a Time column, a Status column, and a connect-boards column to the People Board. Monday has no automatic conflict-detection for double-booking, no chair or room resource model, and no session-duration logic — those MOGO features do not transfer and must be re-evaluated in Monday's workflow tools. We document the recommended board structure in the pre-migration schema plan and configure the columns before data lands.

MOGO billing and accounts-receivable logic has no Monday CRM equivalent — financial reconciliation must be rebuilt

MOGO tracks invoice line items, insurance adjustments, payment plans, and write-offs with a structured financial model. Monday CRM's billing module is a quote and order management tool for sales deals — not a clinical or service billing system. Invoice records migrate as Items on a Billing board with a Status column, but payment reconciliation workflows, insurance write-off logic, and accounts-receivable aging must be rebuilt in Monday's automation system or handled via a separate accounting integration. We flag the accounts-receivable gap in the pre-migration audit and provide a rebuild reference from the MOGO invoice schema.

Monday's daily API rate limits vary by plan tier — large MOGO exports can be throttled during migration

Monday CRM enforces a daily API call limit that varies by plan: 200 calls/day on Free/Trial, 1,000 on Basic/Standard, 10,000 on Pro (soft limit), and 25,000 on Enterprise (soft limit). A MOGO export containing 50,000 patient records, 200,000 appointments, and 30,000 invoices could require 280,000+ API write operations at the Item level. We use Monday's bulk mutation endpoint where available, paginate writes to stay within plan limits, and run large migrations during off-peak hours. If your Monday plan has insufficient daily limits, we recommend upgrading to Pro before migration or using Monday's CSV import for high-volume objects.

Custom MOGO fields require column-type decisions before migration — Monday's 20+ column types each handle data differently

MOGO custom fields (clinical notations, recall preferences, insurance plan codes, referral sources) are stored with type metadata in MOGO's database. Monday CRM represents equivalent data as Columns with specific types: text fields for plain strings, dropdowns for pick-lists, checkboxes for booleans, date columns for dates, and link columns for relationships. Some MOGO field types — such as multi-select pick-lists or structured clinical data — don't map cleanly to a single Monday column type and may require a compound approach (e.g., a dropdown plus a text column for notes). We deliver a column-type recommendation for every custom MOGO property as part of the migration plan, and your Monday admin approves each mapping before migration runs.

MOGO appointment reminders, recall alerts, and recall automations do not migrate — they must be rebuilt in Monday's Recipe builder

MOGO's built-in appointment reminder sequences (email or SMS confirmations, recall alerts, follow-up sequences) are practice-configured automations stored in MOGO's workflow engine. Monday CRM has a separate automation product — Monday Automations using Recipes with triggers and actions — that provides comparable functionality but requires a complete rebuild. We export the MOGO automation definitions (trigger conditions, recipient rules, message templates) as a rebuild reference document for your Monday admin. Recurring calendar-based automations (e.g., 6-month recall) can be rebuilt in Monday using the Date column + Recipe time-trigger.