Migrate from Paradym to Nutshell

Paradym's person records map 1:1 to Nutshell People. Name fields, email, phone, and address map directly. Owner resolution happens by email match against Nutshell users — unmatched owners are flagged before the migration commits any records. If no matching Nutshell user exists, FlitStack assigns the record to a designated fallback owner and logs the discrepancy in the pre-flight report for your admin to resolve post-migration.

If Paradym stores a role designation or tag indicating a record is an unqualified prospect, FlitStack routes it to Nutshell's Lead object rather than Person. The split rule is configurable per your Paradym tagging convention — your migration plan documents the rule before execution.

Paradigm company records map to Nutshell Company objects with a direct 1:1 correspondence for standard fields. Company name, domain/website, and industry sector map directly to their Nutshell equivalents. If Paradym stores a parent-company relationship, it maps to Nutshell's Parent Company lookup field — the parent company record must migrate first so the foreign key resolves correctly, which FlitStack sequences automatically in the migration run order.

Paradym associates a person record with a company via an internal link. In Nutshell, each Person record has a single primary Company lookup. The most-recently-modified association becomes the primary; additional company associations are captured as a custom text field on the Person for admin reference.

Paradym has no native deal object — deal-like records (deal name, amount, status) live in custom fields or as associated activity records. FlitStack extracts these into a Deal record in Nutshell, mapping deal name to Deal.Name and amount to Deal.Value. The target Nutshell pipeline and stage are assigned per your pre-migration stage-mapping configuration.

Any stage-like values stored in Paradym custom fields are mapped value-by-value to Nutshell pipeline stage names. Nutshell pipelines are pre-created in your Nutshell account before the migration runs — FlitStack delivers the pipeline setup plan as part of the migration workbook so your admin creates the right stages in advance.

Paradym engagement records (emails, calls, meetings) map to Nutshell Tasks (for emails and calls) and Events (for meetings). Original timestamps, subject, and linked person/company are preserved. The task owner resolves by email match — unresolved owners land under a migration service account for manual reassignment.

Notes migrate as Nutshell Notes attached to the relevant Person, Company, or Deal record. Rich-text formatting is preserved where possible. Long notes that exceed Nutshell's display limit are truncated with a flag so your admin can review and split them manually post-migration.

Paradym nested object attributes and array attributes (e.g., person.name, address.street) that have no direct Nutshell equivalent are created as custom fields on the target Nutshell entity (Person, Company, or Lead). Nested values are flattened into a text or JSON field as appropriate. Nutshell's field-type constraints (text, number, date, picklist) determine the final storage format.

Paradym stores files attached to credential templates and presentations. These are downloaded and re-uploaded to Nutshell's file storage. Files over Nutshell's 25 MB per-file limit are flagged for manual re-upload by your team. FlitStack generates a file-mapping manifest so nothing is lost during the re-upload step.

Paradym credential sequences and automated follow-up triggers are platform logic, not data records. They cannot be extracted via the API in a form that Nutshell can consume. FlitStack exports the sequence configuration as a JSON reference document that your Nutshell admin uses to rebuild equivalent email sequences and workflow triggers in Nutshell Pro or Business.

Paradym SD-JWT credential templates are a Paradigm-specific identity-issuance construct with no equivalent in Nutshell's CRM model. The template name and any associated metadata are preserved as a text custom field on the linked Person record so your team retains a reference to which credential template was previously associated with each contact.