Migrate from Less Paper Co. to Zoho CRM

Less Paper Co. does not have standalone Contact or Account records — customers are properties of work orders. We split each unique customer into a Zoho Contact (person fields: name, email, phone) and an Account (organization fields: company name, address, industry). If the customer is an individual with no company, the Account still gets created with the individual's name to satisfy Zoho's AccountId lookup requirement on Contacts.

Each Less Paper Co. work order becomes a Zoho Deal. The work order number maps to Deal_Name or a custom Work_Order_ID__c field. Service type, line items, labor calculation, and scheduling window are carried forward as custom fields on the Deal. Status (open, in-progress, completed, cancelled) maps to Zoho Deal Stage via value mapping.

Less Paper Co. line items (service descriptions, quantities, unit prices, parts) are stored per work order. We merge all line items into Zoho's Products module linked to the Deal via Deal Line Items. If the source stores flat JSON or text descriptions rather than structured line items, we preserve the full text in a custom field (Line_Item_Raw__c) and create skeleton Products as a reference.

Less Paper Co. stores scheduling windows with a start date, end date, technician assignment, and travel-time calculation. Zoho Events hold a single Start DateTime and End DateTime — a direct map loses the window structure. We create Scheduled_Start_Date__c, Scheduled_End_Date__c, Technician_Name__c, and Travel_Time_Minutes__c as custom fields on the Deal, and create a Zoho Event for the scheduled date as a calendar reference.

Less Paper Co. stores signatures as image URLs or embedded image data attached to work orders. We download the signature image, re-upload it as a Zoho Attachments on the corresponding Deal, and store the original signature URL in Signature_URL__c for traceability. If the source uses a signing-service webhook URL, we store that URL in Signing_Service_URL__c.

Less Paper Co. generates PDF work order documents. We download each PDF, then re-upload it to Zoho Files attached to the Deal record. The original PDF generation timestamp is preserved in PDF_Generated_Date__c. If the PDF URL is password-protected or session-based, FlitStack fetches it using stored credentials before re-uploading.

Less Paper Co. tracks inventory items and parts consumed per work order. We map inventory items to Zoho Products with a custom Inventory_Item__c flag. Parts used per work order are stored in a custom multi-line field (Parts_Used_JSON__c) or as related Deal Line Items referencing the inventory Products. Vendor information on parts maps to Vendor_Name__c on the Product.

Less Paper Co. vendor records map directly to Zoho Accounts with Account_Type set to 'Vendor'. Vendor contact details (name, phone, email) map to the Account's primary Contact if available. If the vendor is a new organization with only a contact person, we create both an Account (vendor) and a Contact (person) and link them.

Less Paper Co. stores free-text notes and internal comments on work orders. These map to Zoho Notes attached to the corresponding Deal. Original timestamps and the creating user's identity are preserved as note metadata. Rich-text formatting is stripped to plain text if the source uses HTML markup.

Less Paper Co. tracks status transitions (created, assigned, in-progress, completed, invoiced) with timestamps. Zoho Deals have a Stage History built-in, but if the source tracks more granular sub-statuses, we create Status_History__c as a custom text field storing a JSON array of {timestamp, old_status, new_status, user} records for audit continuity.

Less Paper Co. technicians and dispatchers are functional users. We match them by email address against Zoho Users — matched users become the Deal Owner for work orders assigned to them. Technicians without a Zoho user account are flagged before migration; your team either creates Zoho user accounts for them or assigns their records to a fallback owner.

Less Paper Co. purchase orders attached to work orders map to a Zoho custom module (Purchase_Orders__c) if the count exceeds 20 records, or are embedded as custom fields (PO_Number__c, PO_Amount__c, PO_Status__c) on the related Deal. We choose the approach based on the volume of PO data before migration runs.