Migrate from Orderry to Salesforce Sales Cloud

Orderry clients with a single point of contact map to a Salesforce Account with one primary Contact. Clients with multiple service contacts get an Account and multiple Contacts linked via AccountId. Orderry client addresses become the Account shipping/billing address fields. Primary client email becomes Contact.Email.

Work Orders map to Salesforce Cases by default if you use the native service cloud model. If you need Orderry-specific fields (technician, parts used, site location), we create a custom Work_Order__c object with Status__c, Priority__c, Technician__c (User lookup), Location__c, and a Parts_Junction__c junction object for line items. We surface the choice before migration runs.

Orderry products become Salesforce Product2 records. The product name, SKU, unit cost, and description map directly. For selling price, we create PricebookEntry records against your standard price book. Serialized products may also generate Asset records if you track installed equipment per client Account.

Orderry invoices map to Salesforce Orders (activated status) with OrderProduct line items matching the invoice detail. Order Number from Orderry becomes Order.OrderNumber. Invoice date becomes Order.EffectiveDate. Payment status from Orderry is stored as a custom Payment_Status__c field on Order since Salesforce's native order model doesn't have a paid-pending-closed status pick-list.

Orderry employees with active logins map to Salesforce Users. Email match resolves existing Salesforce users directly. For employees who are technicians but not Salesforce users, we create a Contact record on a internal Account and link Work_Order__c.Technician__c to that Contact — your admin decides on licensing after migration.

Orderry locations become either Account shipping addresses (if each location maps to a client site) or a custom Location__c object (if you track internal branch locations independently from clients). We default to Account ShippingAddress for client site locations and create Location__c for internal service depot records.

Orderry estimates map to Salesforce Opportunities in the 'Estimate' stage, or to native Salesforce Quotes if you have CPQ enabled. Estimate line items become OpportunityLineItems or QuoteLineItems. We preserve the estimate total, expiry date, and accepted/rejected status as custom fields since Orderry tracks these states explicitly.

Orderry payments (outside of invoices) create a custom Payment__c object linked to the Order or Account. This preserves payment method, amount, transaction date, and reference number that don't fit into Salesforce's native Order model. We also link Payment__c to the corresponding Order record via a lookup.

Orderry work order notes and internal comments map to Salesforce CaseComments on the linked Case. Timestamps and author (technician name) are preserved. If you use Salesforce Chatter, we can alternatively create FeedItem records for a more interactive thread view — your admin chooses per record type.

Orderry file attachments on work orders, invoices, and client records re-upload to Salesforce Files (ContentDocument) with the parent record linked via ContentDocumentLink. Original file names and create dates are preserved. Files over 25MB are chunked per Salesforce's file size limit.

Orderry custom fields on work orders — such as warranty_type, site_condition, or parts_source — become Salesforce custom fields on the Work_Order__c or Case object. We generate the field metadata (type, pick-list values, validation rules) from Orderry's field definitions and create them in your sandbox before migration data loads.