Migrate from erxes to Nutshell

erxes Contacts map directly to Nutshell People. The primary fields (name, email, phone) translate to standard Nutshell Person fields. We extract custom field values from erxes and validate each against the target field type in Nutshell before insert; any value that violates Nutshell's type enforcement (for example, a text string in a date-typed field) is flagged and either remapped to a text custom field or logged for manual resolution. Owner assignment migrates by email match against Nutshell Users.

erxes Company records map 1:1 to Nutshell Company records. The companyId reference in erxes Links field preserves the association to the related Person. We map industry, size, and website fields to their Nutshell equivalents and transfer custom field values with the same type-validation logic applied to Person records.

erxes Deals map to Nutshell Deals with stage, amount, and responsible user preserved. The key translation is erxes pipeline stage to Nutshell pipeline stage; we confirm the target Nutshell pipeline has matching stage values configured before migration, or we flag a stage-mapping gap that requires Nutshell admin configuration before the Deal import phase begins.

Each erxes Pipeline maps to a Nutshell Pipeline with stage translation. We verify that the destination Nutshell account has pipelines configured with the corresponding stage names and probabilities. If erxes uses multiple pipelines to segment business lines, we create parallel Nutshell pipelines and map Deal records accordingly. Stage IDs are translated to destination stage identifiers during import.

erxes Tasks migrate to Nutshell Tasks with title, description, due date, status, and assigned user preserved. User assignment resolves via email match to the Nutshell User table. Tasks organized into Teams and Cycles in erxes are logged as custom field notes or activity flags since Nutshell does not use a Cycles model; the customer chooses how to represent team-scoping during scoping.

erxes Users (team members with roles) map to Nutshell Users by email address. Role and permission configurations do not transfer because Nutshell's permission model differs structurally; we extract role names as notes and flag the Nutshell admin to reassign permissions manually post-migration.

erxes custom fields on Contacts, Companies, Deals, and Tasks require pre-creation in Nutshell before data import. We extract the field names, types, and options from erxes and create equivalent Nutshell custom fields via the Nutshell custom fields API. Type mapping: erxes text and number fields map to Nutshell text fields; erxes dropdown fields map to Nutshell dropdown with the same option list; erxes date fields map to Nutshell date fields. Any erxes field with no type definition (schema-less ingest) defaults to Nutshell text to avoid import rejection.

erxes multi-channel Conversations (email, SMS, chat, WhatsApp) do not have a direct Nutshell equivalent because Nutshell uses Gmail and Outlook integration rather than a native inbox. We migrate conversation metadata and the most recent message body as a Note attached to the related Person or Company record. Older message threads are logged in a reconciliation document for the customer's admin to review. Message threading order depends on server-side timestamps in erxes; we preserve createdAt values in the Note body for reference.

erxes Channel configurations (email accounts, SMS credentials, chat API keys, WhatsApp Business API credentials) do not migrate. These represent external service credentials that would require re-authentication regardless of migration path. We flag each active Channel in the source erxes instance and list the reconfiguration steps (which credentials to update, which API keys to regenerate) so the customer's admin can restore connectivity in Nutshell's communication settings post-migration.