Migrate from SwiftCRM to Zoho CRM

SwiftCRM Contact is a unified client record combining person and organization data. We split it into Zoho Contact (person-level: name, email, phone, Face ID note) and Zoho Account (organization-level: company name, address, domain). When SwiftCRM stores a company name on the Contact, we extract it, create or match the Account, and link the Contact via the Account Name lookup. Any SwiftCRM relationship type property (family, business, referral) migrates as a custom picklist field on the Zoho Contact.

SwiftCRM Appointments with a defined start and end time migrate to Zoho Event (with Start DateTime, End DateTime, and Location preserved). Appointments stored as reminders without specific time windows migrate to Zoho Task (with ActivityDate from the original timestamp and the SwiftCRM reminder text stored in the Task description). The client link is resolved by finding the migrated Contact or Account record and setting the WhoId or WhatId accordingly. Appointment notification flags from SwiftCRM become Zoho Task Status or Event reminder settings.

SwiftCRM Reminders tied to specific clients map to Zoho Tasks. The SwiftCRM reminder text becomes the Task Subject or Description. The linked client Contact resolves to a Zoho WhoId. If the reminder also references an appointment, we resolve the associated Event in Zoho via the WhatId link. Standalone reminders without a client link are imported as Tasks with no WhoId but with a custom field swift_reminder_type__c set to standalone.

SwiftCRM E-Docs are client documents stored within or alongside the contact record. We export each file, name it with the original document title, and attach it to the corresponding Zoho Contact or Account record via Zoho's attachment API. If the E-Doc contains structured text rather than a binary file, we migrate it as a Zoho Note linked to the Contact. File metadata (document type, creation date, tags) migrates to custom fields on the Note or as a tag on the attachment.

SwiftCRM notification history tied to client interactions migrates as Zoho Tasks with a custom field swift_notification_source__c set to notification. The notification body text becomes the Task Subject. The timestamp is preserved in ActivityDate. If the notification triggered an appointment or reminder, we link the Task to the corresponding migrated record via WhatId. Notifications without a linked record become standalone Tasks with a custom field swift_context__c set to general.

SwiftCRM tracks family and business relationship structures between contacts (e.g., spouse, business partner, referral source). We evaluate whether these map better to Zoho custom picklist fields on the Contact (for simple relationship type labels) or to a lightweight related-list custom module (for directional relationships like referrer/referral). The customer chooses during scoping. We preserve both the related contact name and the relationship type label.

SwiftCRM beta-tier custom fields vary by account. We audit every available custom field during scoping, capture its data type and picklist values, then pre-create matching custom fields in Zoho CRM before any data loads. Zoho's 300-field limit per module and 5-lookup-field cap are checked against the total custom field count. Any fields exceeding these limits are flagged and discussed with the customer for consolidation or alternative mapping.

SwiftCRM user accounts and basic permissions migrate to Zoho Users. We match SwiftCRM user email addresses to Zoho User records, resolving the OwnerId reference on all migrated records. Any SwiftCRM user without a matching Zoho User goes to a reconciliation queue for the customer to provision before record import continues. Role and permission sets do not migrate as code; we deliver a Zoho permission-role inventory document for the admin to configure post-migration.

Because SwiftCRM is in active beta, we take a schema validation snapshot as close to migration day as feasible. Any fields present in scoping that have been renamed, removed, or had their type changed since scoping are re-mapped against the live snapshot. If more than 30 days elapse between scoping and cutover, we re-validate the SwiftCRM schema before beginning the Zoho migration to catch any beta-driven changes. This freeze-and-validate step prevents silent field drops from incomplete mapping.

SwiftCRM E-Docs carry metadata beyond the file itself: document type, client association, creation timestamp, and any tags. We preserve this metadata in Zoho custom fields on the Note or Attachment record so that document classification and filtering work without the original SwiftCRM interface. The customer confirms which metadata fields are business-critical during scoping.