Migrate from SwiftCRM to monday CRM

SwiftCRM Contacts store name, relationship type, Face ID-protected confidential data, and client-specific metadata. We map these 1:1 to Monday.com People items, preserving name fields, phone numbers, email addresses, and any client classification properties as custom text or dropdown columns on the People board. The Face ID protection flag from SwiftCRM migrates as a custom text column noting data sensitivity; Monday.com does not have a native biometric access control equivalent so the physical device-level protection does not carry forward into the new system.

SwiftCRM Appointments include client link, scheduled time, reminder configuration, and notification context. We map these to Monday.com Items on a dedicated CRM board with Start Date and Due Date columns preserving the original timestamp. The client link becomes a Person or Organization connection column on the item. Reminder flags from SwiftCRM map to subitems or task sub-items with due-date columns on the appointment item, though the notification delivery mechanism must be rebuilt in Monday.com automations post-migration.

SwiftCRM Reminders tied to specific contacts or appointments split into Monday.com Subitems on the parent appointment item or standalone Task items on a Reminders board linked back to the Person item. Due dates and reminder text migrate to the corresponding Monday.com columns. The SwiftCRM notification delivery mechanism (push notification or alert) is not a migratable artifact; we document the reminder configurations for the customer's admin to rebuild as Monday.com automation triggers.

SwiftCRM E-Docs are files organized within client records and receive specific praise in reviews for their structure. We export all attached files, preserving file names and folder structure, and attach them to the corresponding Person or Organization item in Monday.com CRM via the file column type. Folder hierarchy from SwiftCRM maps to Monday.com Group labels or a separate Documents board linked back to People items.

SwiftCRM tracks family and business relationship structures between contacts (for example, spouse-of, business-partner-of, referrer-to). We preserve these as custom dropdown columns on the Person item (relationship_type) or as Monday.com Item connection columns linking two Person items with a labeled relationship. The customer chooses the relationship model during scoping based on how their team will use the data in Monday.com boards.

SwiftCRM beta-stage custom fields vary by account tier and may include client-specific properties not available in the standard Contact object. We audit all available custom fields during scoping, map each to the equivalent Monday.com column type (dropdown for picklists, text for free text, number for numeric values, date for timestamps), and create the columns on the relevant boards before data import begins. Any custom fields unavailable in the Standard or Basic Monday.com CRM tier are flagged during scoping.

SwiftCRM user accounts and basic permissions map to Monday.com Team Members. We map SwiftCRM users by email match to Monday.com User records and assign them to the relevant CRM workspace. Any SwiftCRM user without a matching Monday.com account goes to a reconciliation queue for the customer's admin to provision before record reassignment begins.

Notification history tied to client interactions in SwiftCRM (for example, appointment confirmation sent, reminder delivered) migrates as Note items or text columns on the relevant Person or Appointment item in Monday.com CRM. The notification context (what triggered it, when) is preserved as descriptive text. Monday.com does not have a native notification history log, so this migrates as activity context rather than a functional notification system.