Migrate from Striven to Freshsales

Striven's Customer records combine person-level contact data (name, email, phone) with company-level data (company name, address, industry). We split each Customer into a Freshsales Contact (person fields) and an Account (company fields) linked by the AccountId lookup. The Account is created first, then the Contact is inserted with the AccountId reference resolved. Any type-level Custom Fields scoped to specific Customer Types are audited during discovery and mapped to Freshsales Contact or Account custom fields based on the entity subtype.

Striven Items (products and services required before Sales Orders or Purchase Orders can be created) map to Freshsales Product2 records. We map the item name to Product Name, item code to Product Code, and unit price to Standard Price. Inventory quantities on hand are noted as a Product custom field in Freshsales since the standard object does not track on-hand quantities natively.

Striven Sales Orders map to Freshsales Deals. The linked Customer resolves to the Account-Contact pair created during the split. Sales Order status maps to Freshsales Deal stage (Open, Closed Won, Closed Lost). Line items from the Sales Order become Deal Line Items or product-specific custom fields depending on the destination Freshsales plan. Order types that drive type-level Custom Field visibility in Striven require explicit mapping during discovery.

Striven Projects (with phases, milestones, and custom fields) have no direct Freshsales equivalent. We scope this as a configuration decision during discovery: Projects map to Freshsales Deals with a Project record type if the customer treats them as sales pipeline opportunities; they map to Freshsales Custom Modules (Enterprise tier) if the customer maintains a project tracking use case that should live within the CRM. Task hierarchies under Projects map to Freshsales Tasks attached to the parent Deal or Custom Module record.

Striven Tasks under Projects map to Freshsales Tasks with assignees preserved. Subtask hierarchies and dependency relationships require explicit mapping: parent task references become Freshsales WhatId lookups or custom task-link fields. We preserve task status, priority, due date, and the original Striven timestamp for activity timeline ordering.

Striven Notes (attached to any entity) map to Freshsales Note records linked via ContentDocumentLink to the parent Contact, Account, or Deal. Note body migrates as rich text. We preserve the original created date for timeline ordering. Document attachments themselves are not migrated as binary files unless the customer's Striven export exposes a file URL; we document the attachment associations for manual re-linkage post-migration.

Striven supports both global-level Custom Fields (visible on all records of a type) and type-level Custom Fields scoped to specific entity subtypes. We audit the full custom field schema during discovery to classify each field by scope and map to Freshsales Contact, Account, Deal, or custom module custom fields accordingly. Type-level fields that were only visible on specific Striven entity subtypes are mapped to the equivalent entity in Freshsales; fields without an equivalent destination are flagged for manual cleanup after migration.

Striven Vendors, Employees, Invoices, Bills, and Chart of Accounts records have no Freshsales equivalent. Freshsales is a CRM without accounting, AP/AR, or HR modules. We document these records in a Data Inventory worksheet with record counts and field schemas so the customer can decide whether to archive them in a spreadsheet, migrate them to a separate accounting tool, or re-enter them manually. Vendor and Employee records are held in a reconciliation queue during migration scoping and do not block CRM record import.