Migrate from Olqan to Nutshell

Olqan Contacts map to Nutshell People. Standard fields (name, email, phone, company association) migrate directly. Lifecycle stage values from Olqan (lead, customer, evangelist, or custom labels) are preserved in a custom field olqan_lifecycle_stage__c on the Person record. If Olqan records include a lifecycle stage indicating an unqualified prospect, we evaluate splitting to Nutshell Lead during scoping.

Olqan Companies map to Nutshell Companies. We map company name, address, industry, size, and association records. The company domain from Olqan becomes the Company website field and acts as the dedupe key during import. Account must be created before any linked Person import so that the lookup relationship is satisfied at the moment of Person insert.

Olqan Deals map to Nutshell Leads, not directly to Opportunities. In Nutshell's CRM model, Leads are the primary sales-tracking object before conversion to People and Companies. The Olqan deal value, stage name, and probability migrate to Lead value and status fields. We preserve the Olqan pipeline name in a custom field for reference during post-migration review.

Olqan pipeline stage names vary by organization configuration. We extract the current stage labels and probabilities and map them to Nutshell Lead Status values during scoping. If the customer uses multiple pipelines in Olqan, we document each pipeline-to-status mapping for the customer's admin to configure in Nutshell settings post-migration.

Olqan standalone Tasks (not nested within Projects) migrate to Nutshell Tasks. Task title, description, assignee (resolved by email match to Nutshell User), due date, and status migrate. Subtask nesting from Olqan is flattened to a flat task list since Nutshell Tasks do not support hierarchical subtasks natively.

Olqan custom fields on Contacts, Companies, and Deals migrate to Nutshell custom fields for People, Companies, and Leads. We pre-create the destination custom field schema in Nutshell before any data import. Nutshell supports text, long text, currency, date, number, and checkbox types. We type-map Olqan field types to the closest Nutshell equivalent and flag any unsupported field types for the customer's admin to resolve.

Olqan owners (CRM module users) map to Nutshell Users by email address match. Any Olqan owner without a matching Nutshell User email goes into a reconciliation queue for the customer's admin to provision before the Person and Lead import phases. Owner assignments on Deals and Tasks are preserved as the assigned Nutshell User.

File attachments on Olqan Contacts, Companies, and Deals migrate as linked files in Nutshell. We preserve the original filename, upload date, and association to the parent record. Large attachments (over 10 MB) are chunked and re-assembled during load. Attachments from Olqan's Project, HR, and Finance modules are out of scope for this CRM migration.