Migrate from SwiftCRM to Nutshell

SwiftCRM Contacts map directly to Nutshell People records. The SwiftCRM client record (name, relationship type, Face-ID-protected fields) migrates to Nutshell's standard People fields plus any custom fields audited during scoping. SwiftCRM relationship types (family, business) map to Nutshell custom fields or relationship-type picklists. We use the SwiftCRM contact identifier as the external_id for dedupe validation during import.

SwiftCRM Contacts that represent unqualified prospects (early-stage relationships with no active engagement history) may split to Nutshell Leads if the customer's sales process distinguishes between People records (existing clients) and Lead records (prospective contacts). We determine the split rule during scoping based on the customer's contact lifecycle stage if tracked in SwiftCRM custom fields. Unqualified contacts land in Nutshell as Leads with original relationship type preserved in a custom field.

SwiftCRM relationship structures between contacts (family and business relationship links) that represent organizational connections map to Nutshell Company records. We extract relationship metadata during scoping to determine whether the SwiftCRM contact network should become Nutshell People with a Company affiliation or People linked via a Company record. The customer chooses the mapping strategy during discovery.

SwiftCRM appointments with client links and reminder settings map to Nutshell Activity records. We preserve the original appointment timestamp as the Activity date, the client association as a link to the migrated Nutshell Person, and any appointment notes as the Activity description. Recurring appointment patterns are flagged during scoping for manual rebuild as Nutshell tasks or calendar sync depending on the recurrence complexity.

SwiftCRM reminders tied to specific clients or appointments map to Nutshell Task records. The reminder text becomes the Task subject, the due date maps to the Task due date, and the linked client association preserves via the Person link. Completed vs pending status transfers to Task completion status. SwiftCRM-native notification context (e.g., reminder type) migrates as a custom Task field.

SwiftCRM notification history tied to client interactions does not map to a distinct Nutshell object. We migrate notification records as Note or activity records attached to the corresponding Person, preserving timestamp, notification type, and content. If the notification volume is high (hundreds per client), we summarize the notification history and flag it for the customer admin to determine retention scope.

SwiftCRM client documents organized within the platform migrate as file attachments in Nutshell, linked to the corresponding Person or Company record. We export all attached files in their original format (PDF, image, document), batch them by contact, and upload to Nutshell with a naming convention that preserves the original document structure. Large file volumes may require chunked upload with Nutshell API rate-limit handling.

SwiftCRM beta-stage custom fields vary by account tier and may include relationship-type metadata, client classification flags, or industry-specific properties. We audit all available SwiftCRM custom fields during scoping, map each to the equivalent Nutshell custom field type (text, date, number, picklist), and create the destination fields in Nutshell before migration begins. Beta-tier custom fields that cannot be mapped to Nutshell types are flagged for customer review.

SwiftCRM user accounts and basic permissions map to Nutshell User records. We resolve users by email match. Any SwiftCRM user without a matching Nutshell account is held in a reconciliation queue for the customer's admin to provision before record import resumes. SwiftCRM Face-ID-linked access permissions do not have a direct Nutshell equivalent and are not migrated.