Migrate your Less Paper Co. data

Work Orders are the core entity, but field names, custom properties, and statuses are unique to each deployment. We map the source field names to the destination schema during the pre-migration schema audit. Nested line items and labour calculations are preserved by flattening them into structured rows.

Customer records (name, contact info, address, service history) map cleanly between most FSM platforms. We match on email and company name as primary keys and deduplicate where duplicates exist.

Scheduling data includes technician assignment, time slots, travel time, and availability windows. We preserve the technician-to-appointment relationship but note that availability patterns may need re-entering in the destination if the scheduling engine uses different logic.

Each deployment stores inventory items and line items differently — some use a separate Items table, others embed them in the Work Order. We normalise these into a canonical structure before writing to the destination.

Vendor records (name, contact, associated purchase orders) are migrated, but vendor-specific pricing rules tied to custom formulas may require manual review post-migration.

Purchase Orders reference vendors and inventory items. We migrate the PO header and line items but flag any vendor-specific discount logic that cannot be expressed in the destination schema.

Electronic signatures captured on Work Orders are stored as image blobs or encoded strings. We preserve them in the migrated Work Order records as attachments, ensuring the signature image is intact in the destination.

Payment records include amount, method, timestamp, and Work Order linkage. We migrate payment history as-is but note that payment gateway tokenisation does not carry over — customers will need to re-tokenise payment methods in the new platform.

Photos, videos, and PDFs uploaded to Work Orders are exported as binary blobs or URL references. We preserve the original filenames and attach them to the correct Work Order in the destination.

Free-form notes and sub-tasks attached to Work Orders or Customers are migrated as text fields, preserving timestamps and author attribution where available.

User records include name, role, and scheduling assignment. We map Users to the destination's equivalent user object, but permission sets and role configurations are destination-specific and require manual review.

Every Less Paper Co. deployment has custom fields unique to the business. During scoping, we catalogue every custom property and map it to either a native destination field or a custom field in the destination. No custom property is dropped without explicit customer sign-off.