Migrate from OnePageCRM to Nutshell

OnePageCRM Contact records map directly to Nutshell People. Standard fields (name, emails, phones, addresses, social URLs) map to equivalent Nutshell Person fields. The Next Action date and text from OnePageCRM transfer to a custom Next Action field in Nutshell since Nutshell does not have a native next-action inbox model. Custom contact fields map to Nutshell Person custom fields after pre-creation during schema setup.

OnePageCRM Organization records map to Nutshell Company records with direct field mapping for name, phone, address, and custom company fields. The contact-to-organization linkage is preserved by matching on organization name as the deduplication key and resolving the Nutshell Company ID before Person import so that the relationship is satisfied at insert time.

OnePageCRM Deals map to Nutshell Opportunities. The deal name, amount, close date, margin, commission, and cost fields map to equivalent Nutshell Opportunity fields. Pipeline and stage assignments from OnePageCRM transfer to Nutshell's pipeline and status fields. Closed deals (Won/Lost) migrate with their status preserved as a custom closed_status field in Nutshell.

OnePageCRM contact-level custom fields map to Nutshell Person custom fields. Both platforms require custom fields to exist before data lands. We provide a pre-migration checklist during scoping that confirms all source custom fields are pre-created in Nutshell before import, and we drop any that have no equivalent field type in the destination.

Organization-level custom fields behave identically to contact custom fields. We check schema parity during scoping, pre-create fields in Nutshell, and map to equivalent company custom fields in the destination. Any fields exceeding Nutshell character limits or using unsupported field types (e.g., multi-select with too many values) are flagged and resolved before migration.

Tags assigned to OnePageCRM contacts transfer as Nutshell tags. Both platforms use a flat tag namespace without hierarchy. We preserve the tag values exactly and run post-import deduplication on the tag set to remove any orphaned or duplicate tags. The customer chooses whether to use Nutshell's tag field or a multi-select picklist during scoping.

OnePageCRM Predefined Items representing products or services used in deal creation map to Nutshell Products. Name, price, quantity, and grouping information transfer directly. Product groupings in OnePageCRM map to Nutshell's product category or are flattened into the product name if no equivalent grouping structure exists in the destination.

OnePageCRM Predefined Actions (saved task templates assigned to contacts) are mapped to Nutshell task records rather than as reusable templates. The template name and action steps transfer as a series of linked tasks on the target Person record. We do not migrate Autoflow workflows as automation code; instead we deliver a written inventory of every active Predefined Action with its trigger, conditions, and recommended Nutshell equivalent for the customer to rebuild.

OnePageCRM notes and call logs attached to contacts export as plain text in the contacts dataset. We map these to Nutshell Note records linked to the target Person or Company. Note body text transfers as-is. Call duration and call metadata from call logs become Nutshell Activity records of type Call. Email body content and attachments do not export from OnePageCRM natively and are documented as a known gap requiring acceptance before migration.

OnePageCRM contact statuses (e.g., Prospect, Qualified, Customer) define where a contact is in the sales pipeline. We capture the full status taxonomy and map each status to an equivalent Nutshell Person status value or create custom status values in Nutshell if the source statuses do not map directly. The status taxonomy is preserved for reporting continuity.

OnePageCRM Lead Sources (classifying how a contact entered the CRM) map to Nutshell lead source fields on Person records. The pre-populated list from OnePageCRM is recreated as Nutshell custom lead source values. Any lead source values not supported by Nutshell's field type are converted to a text field and documented for the customer's admin to reconcile post-migration.