Migrate from Less Paper Co. to Salesforce Sales Cloud

Less Paper Co. Customer records hold both company and person data in one flat structure. We split them: company name + address maps to Account.Name and Account.BillingAddress; primary contact name + email + phone maps to Contact records linked via AccountId. For sole-proprietor customers without a company name, we create an Account using the customer name and attach the Contact under it.

Contact-level fields migrate directly: email to Contact.Email, phone to Contact.Phone, mailing address to Contact.MailingStreet / MailingCity / MailingState / MailingPostalCode / MailingCountry. Less Paper Co. stores these as flat customer properties; we parse them into Salesforce's compound address field structure.

No native Salesforce object maps 1:1 to a work order. If the source records represent field-service jobs with status transitions, we create a custom Work_Order__c object with fields for Work_Order_Number__c, Status__c, Priority__c, Assigned_Technician__c (lookup to User), Scheduled_Date__c, and Completed_Date__c. If the records represent billable engagements, they map to Opportunity with custom fields. We determine the mapping strategy during the sample migration review.

Less Paper Co. work-order statuses (e.g., Pending, In Progress, On Hold, Completed, Cancelled) map to a custom pick-list field on the custom Work_Order__c object. We preserve the source status labels and map them value-by-value to Salesforce pick-list values. Status-transition timestamps from the source are stored as custom datetime fields for audit continuity.

Each line item on a Less Paper Co. work order splits into either an OpportunityLineItem (if tied to a Salesforce Opportunity) or a child Work_Order_Line_Item__c custom object with a lookup to the parent Work_Order__c. Part number, quantity, unit price, and description map to custom fields. We match the part description to an existing Salesforce Product2 record or create one during migration.

Less Paper Co. appointments map to Salesforce Event records. We set Event.Subject to the work-order reference, Event.StartDateTime and Event.EndDateTime from the appointment time window, Event.WhoId to the linked Contact, and Event.WhatId to the Work_Order__c record. We preserve the technician assignment and service type in custom fields on the Event for reporting parity.

Less Paper Co. captures e-signatures on work orders. We download each signature image or PDF, re-upload it to Salesforce as a ContentVersion (Files), and link it to the corresponding Work_Order__c record via ContentDocumentLink. Original capture timestamp and signatory name are preserved as custom metadata fields on the content record.

Less Paper Co. inventory items become Salesforce Product2 records. Product Name maps to Product2.Name, part number to Product2.ProductCode, description to Product2.Description, and unit cost to a custom Unit_Cost__c field. Standard PricebookEntry records are created for the org's default pricebook to enable OpportunityLineItem and Work_Order_Line_Item__c pricing.

Less Paper Co. technician and staff accounts are matched to Salesforce Users by email address. Unmatched technicians are flagged before migration; the client either creates Salesforce User accounts for them or assigns their work orders to a fallback OwnerId. We do not create Salesforce Users programmatically — that requires admin action within the destination org.

Free-text notes attached to work orders or customers in Less Paper Co. migrate as Salesforce Notes linked to the corresponding Account, Contact, or Work_Order__c record. Original author and create timestamp are preserved in the Note.Body header. Rich-text formatting is simplified to plain text where necessary for Salesforce Note compatibility.

Less Paper Co. stores any custom-named properties on work orders (e.g., Service_Type__c, Dispatch_Route__c, Customer_Preferred_Date__c). We create corresponding custom fields on the Work_Order__c object with the __c suffix, using the closest Salesforce field type (pick-list for enumerated values, text for strings, checkbox for booleans, number for numerics). Field-level mapping is reviewed during the sample migration.

Less Paper Co. processes payments against work orders. Salesforce Sales Cloud does not have a native payment object; payment records are preserved as custom fields on the Work_Order__c (Payment_Status__c, Payment_Method__c, Amount_Paid__c) or stored in a related custom object. Full accounting records should live in an ERP — we do not migrate payment ledger data into Salesforce's finance objects.