Migrate from Panacea to monday CRM

Panacea's relational patient-to-client links require board-linking setup in monday CRM before migration

Panacea stores Patients with a foreign key to the Client record — a simple N:1 relationship. In monday CRM, linking a Patient item to its Owner Contact requires the Link to Item column to be configured on the Patients board before any Patient items are created. If this column is added after records exist, monday does not backfill the links automatically. FlitStack sequences the migration so the Contacts board is migrated first, Link to Item columns are configured, and then Patient items are created with the link resolved at write time. The monday CRM admin must pre-create the Patients board with the correct column type — this is a planning-step requirement, not a post-migration fix.

monday CRM's column type determines what data you can store — changing types after migration orphans history

monday CRM columns have fixed types: a Text column cannot become a Number column, a Date column cannot become a Status column without losing the existing data in that column. Panacea stores weight as numeric values and species as text, but if the migration maps these to the wrong column type during setup, correcting the type post-migration requires rebuilding the column and losing all migrated values. FlitStack's sample migration step validates column type alignment before the full run — this catches the mismatch before data lands. Teams migrating from Panacea's flat schema should treat monday column type selection as a schema design decision made during the discovery phase, not during the migration run.

monday CRM API rate limits can throttle large migration batches on lower plans

monday CRM enforces daily API call limits that vary by plan: Free/Trial accounts are capped at 200 calls/day, Basic/Standard at 1,000 calls/day, Pro at 10,000 calls/day (soft limit), and Enterprise at 25,000 calls/day. A Panacea migration with 20,000+ records generating multiple Item creates, column updates, and link resolutions can exhaust lower-tier limits mid-run, causing partial failures. FlitStack monitors the Complexity and Daily limits during the migration run and implements exponential backoff with retry logic. For Standard-plan accounts, we batch writes to stay within the 1,000-call ceiling. Enterprise accounts have headroom for higher throughput without throttling.

monday CRM does not natively support sub-item-level file attachments — files on Subitems require workarounds

Panacea stores lab results, consent forms, and medical images as file attachments on Patient records. monday CRM's Files column works on Items but not on Subitems — vaccination records and prescription logs that migrate as Subitems on the Patient board cannot carry file attachments natively. FlitStack handles this by attaching files to the parent Patient Item and storing a file reference URL in a Text column on the Subitem. This preserves the file but requires the monday CRM admin to open the parent Item to access the attachment rather than viewing it from the Subitem directly.

Clinical alerts and appointment reminders do not exist as data records in Panacea and cannot migrate

Panacea's appointment reminder logic and clinical alerts (vaccination due, medication refill, annual check-up) are platform-native workflow triggers, not stored data records. They do not appear in Panacea's export — there is no API endpoint returning reminder configuration as structured data. monday CRM's automation builder is the rebuild target, but the rebuild cannot be automated because the original trigger logic is not exported. FlitStack delivers a Reminder Configuration Reference document listing each active alert by Patient, by type, with its trigger condition and frequency so the monday CRM admin can reconstruct the automations manually in monday's automation builder post-migration.