Migrate from Profi to Nutshell

Profi has no native Company object — Nutshell's Company field on Person records is unpopulated after migration without manual linking

Nutshell requires a Company record to be associated with a Person via the Company dropdown field. Profi stores organization name as a flat contact property, not as a separate entity. After migration, every Person record in Nutshell will have a blank Company field unless your team creates Nutshell Company records first and maps them back to the Person records. FlitStack can pre-create Company records during migration by deduplicating the organization_name values from Profi and linking them to the corresponding Person records using the Company field — but this requires the Company records to be loaded before the Person import so that the lookup IDs resolve at insert time.

Nutshell Deals require a configured pipeline and stage values before deal records can be inserted

Nutshell does not allow Deals to be created without an active pipeline and at least one defined stage. Profi subscriptions have status values (Active, Cancelled, Completed) but no pipeline concept. Before the migration runs, your Nutshell admin must create at least one pipeline (e.g., 'Coaching Revenue') with stage values such as New, In Progress, Contract Sent, Won, and Lost. FlitStack delivers a pipeline configuration guide as part of the migration plan. If no pipeline exists when the migration runs, deal insert will fail for all subscription records. We validate pipeline configuration during the sample migration phase and flag any missing setup before the full run.

Course enrollment data has no native equivalent in Nutshell — it becomes custom fields and Notes

Profi tracks course enrollments, completion percentages, curriculum progress, and quiz scores as person-level records. Nutshell has no native course-enrollment or curriculum object. FlitStack maps enrollment status to a custom pick-list field (Enrollment_Status__c) and course name to a custom text field (Course_Name__c) on the Person record. Detailed progress and quiz data is preserved as Notes attached to the Person, but it is not queryable as structured fields. Teams that rely on course progress data for reporting should configure Nutshell custom reports using the custom fields after migration, or use a third-party reporting integration.

Profi session history replayed as Nutshell Tasks may trigger Nutshell's activity notification rules

When FlitStack bulk-inserts session history as Nutshell Tasks, any active workflow rules or automation triggers in Nutshell that fire on Task creation (such as email notifications to assigned owners or CRM updates on task completion) will fire for every migrated session record. This can generate a flood of notifications at go-live if those rules are not identified and paused before the migration run. We provide a Nutshell automation audit checklist before the migration so your admin can disable or scope down notification rules during the bulk import window.

Profi workflows, automations, and course-delivery logic do not migrate — they must be rebuilt in Nutshell

Like all migration tooling, FlitStack migrates data and schema only. Profi's automation rules (e.g., enrollment triggers, session reminders, billing notifications) and course-delivery logic (drip content, completion gates, email sequences tied to course progress) are platform-specific and cannot be represented in Nutshell's data model. We export your Profi workflow definitions as a reference document for your Nutshell admin to rebuild in Nutshell's automation tools (Task Rules, Email Sequences, Webhooks). Any email sequences you built in Profi for client follow-up will need to be recreated from scratch in Nutshell's Sales Email sequences feature.