Migrate from coreplus to monday CRM

Monday CRM API daily rate limits throttle large appointment migrations

Monday CRM enforces daily API call limits that vary by plan tier: 200 calls/day on Free, 1,000 on Basic/Standard, 10,000 on Pro, and 25,000 on Enterprise. CorePlus accounts with 10,000+ appointment records can exceed the Pro daily limit during ingestion, causing DAILY_LIMIT_EXCEEDED errors. FlitStack AI batches writes against the applicable tier limit, inserts at 80% of the daily quota, and retries with exponential backoff on limit-hit responses. Large migrations on Standard-tier accounts may require migration spread across two calendar days or a temporary upgrade to Pro for ingestion.

CorePlus practitioner availability has no native Monday CRM equivalent

CorePlus stores practitioner availability as structured time slots per day of week, per location. Monday CRM has no native scheduling engine — appointments and availability must be managed via custom columns on item records or through a third-party scheduling integration such as Calendly or Simplybook. We migrate availability as day-of-week and time-range columns on a Practitioner Availability board, but the automated slot-filling behavior that CorePlus provides must be rebuilt using Monday CRM automations or a connected scheduling tool. Teams relying on CorePlus availability matching should plan for a scheduling integration as part of their Monday CRM setup.

CorePlus custom client fields require manual column creation in Monday CRM before ingestion

Monday CRM custom columns are board-scoped and must be created before item records are ingested. CorePlus accounts with more than five custom client properties (e.g., health fund, emergency contact, referral source, billing notes) require pre-migration column setup in the Monday CRM Contacts board. If columns are not created in advance, FlitStack AI creates them during the migration run, but the column type must match the data — a mismatch between a CorePlus free-text field and a Monday CRM date column, for example, causes the value to drop. We validate column types against source field metadata before ingestion and flag mismatches for resolution.

Monday CRM board-based linking does not enforce referential integrity the way CorePlus does

CorePlus enforces referrer-client and practitioner-appointment relationships at the database level. Monday CRM links between boards (e.g., linking an Invoice item to its Client item) are cosmetic column links — there is no cascade delete or foreign-key constraint. If a CorePlus client record is deleted post-migration, the linked appointment and invoice items in Monday CRM retain the broken link. FlitStack AI generates a migration manifest that lists every source relationship as a custom Source_Relationship column on each item, allowing admins to rebuild links manually or via automation if source records are later modified.

Invoice totals and tax calculations from CorePlus do not auto-replicate in Monday CRM

CorePlus invoice amounts may include GST, discounts, and payment-on-account adjustments calculated at the time of generation. Monday CRM number columns store static values — there is no formula engine at the item level that auto-recalculates invoice totals from line items and tax rates. We migrate the final invoiced amount as a plain number column. If CorePlus invoices contain multiple line items with separate tax treatment, we flatten them into a single total amount and store the line-item breakdown as a text or subitem note. Rebuilt invoice logic (e.g., GST calculation formulas) must be implemented as Monday CRM formula columns or as a separate billing integration.