Migrate from Orderry to Freshsales

Orderry clients stored as individuals (first name, last name, email, phone, address) map directly to Freshsales Contact. Email is the unique identifier for dedup and delta-run matching. Original create date is preserved in a custom datetime field since Freshsales CreatedDate reflects the migration timestamp.

Orderry clients stored as organizations (company name, domain, address, industry) map to Freshsales Account. Account.Name maps from Orderry company_name. Industry values require value-by-value mapping against Freshsales pick-list defaults — unmapped values default to 'Other'. We validate every source industry label against the Freshsales pick-list during the pre-migration audit and flag any non-matching values so your admin can decide how to handle them before extraction begins.

When an Orderry client record has a linked company, the person migrates as a Freshsales Contact and the organization as a separate Freshsales Account. The Contact-Account relationship is created via Freshsales Account Contact Relationships so both entity types remain queryable independently. This split preserves the relational integrity that Orderry represents through the linked company field while fitting Freshsales' normalized data model where individuals and organizations are distinct objects with a relational link.

Orderry work orders have no direct Freshsales equivalent. We map the work order to a Freshsales Deal: Deal Name from Work Order number + client name, Amount from total invoice value, Stage from ticket status (New → 'New', In Progress → 'Qualification', Ready → 'Value Proposition', Issued → 'Closed Won'). Orderry ticket type, priority, assigned technician, and status timestamps become custom fields on the Deal.

Orderry ticket statuses (New, In Progress, Under Review, Ready, Issued, Pending, Cancelled) map to Freshsales Deal Stage values per pipeline. We preserve the original status-transition timestamps as custom datetime fields so Freshsales reports can reconstruct the work-order lifecycle. The value-mapping spreadsheet defines every source status to destination stage correspondence, and unmapped statuses default to the first stage in the target pipeline pending admin review.

Orderry work-order line items (product name, quantity, unit price, tax) migrate as Freshsales Products attached to the corresponding Deal via Deal Products. Each line item creates a product record if it does not already exist in Freshsales, then creates a Deal Product entry linking quantity and price at migration time.

Orderry Estimates (customer-facing price quotes) map to Freshsales Deals with a custom field storing the original Estimate ID and link. Estimate status (Draft, Sent, Approved, Declined) is preserved as a pick-list custom field on the Deal since Freshsales does not have a native estimate object.

Orderry Products (name, SKU, price, cost, stock quantity) map directly to Freshsales Products. Orderry stock_quantity and warehouse location map as custom number fields since Freshsales Products have no native inventory or multi-warehouse model — your team manages stock levels outside the CRM.

Orderry Invoices (number, date, total, payment status) migrate as Freshsales custom fields on the corresponding Deal. The original invoice number and payment status are stored in custom text and pick-list fields. Freshsales does not have a native invoicing object — invoice PDFs are preserved as file attachments on the Deal record.

Orderry Payments (amount, method, date, linked invoice) migrate as custom fields on the Account and Deal for reference. Payment method (Cash, Card, Transfer, etc.) maps as a pick-list custom field. Full payment transaction history is stored as a note on the Account.

Orderry employee records (name, email, role) are matched against Freshsales users by email. Unmatched employees are flagged before migration — your team either creates Freshsales user accounts first or assigns records to a fallback owner. Role labels (Technician, Admin, Manager) become a custom pick-list on the User record.

Any custom fields created in Orderry (text, number, date, pick-list, checkbox, currency types) require Freshsales custom field creation before migration. We deliver a custom-field setup manifest listing each source field name, type, and destination object so your Freshsales admin creates them in advance. Pick-list custom fields require value-by-value mapping where label names diverge.