Migrate your Fame Service data

Customers are the primary contact entity, storing name, company, address, phone, email, and a communication history log linked to work orders and quotes. We map customer records 1:1 in most migrations. Where the destination uses a separate Account/Contact model, we split the company record and link it to the individual contact.

Work Orders are the central operational entity, capturing job type, status, priority, assigned technician, scheduled date/time, site address, asset linked to the job, line items for parts used, and notes. We preserve the full status history on each record. Migrations between platforms require mapping the source Work Order stages to the destination pipeline stages.

Assets represent equipment or installations at a customer site, with serial number, model, install date, warranty end date, and linked customer. Not all FSM platforms expose a separate Asset object; some treat assets as custom fields on Work Orders. We flag this during scoping and merge asset data into the Work Order record when the destination lacks an Asset object.

Inventory tracks parts and equipment stocked in warehouses or on vehicles, with quantity, location, bin assignment, and min/max thresholds. Historical inventory transactions and cost basis may not be fully portable depending on destination schema. We map the current stock snapshot and flag whether the destination tracks multi-location inventory separately.

Employee records cover technicians and field staff with role, department, skills, and contact details. Where Fame Service stores employees in a separate HR module, we can migrate them as Users with a role assignment in the target system. Skills or certifications are treated as custom fields and require explicit mapping.

Service Contracts link recurring SLA terms, billing frequency, and covered assets to a customer account. Contracts are often stored as PDF attachments or structured records with date ranges. We migrate the structured contract data fields and flag PDF attachments for manual re-upload or ingestion via document migration.

Custom fields added to any standard object (Work Order, Customer, Asset) require field-level mapping to the destination. We extract the custom field schema during discovery, map each to a destination field by name or type, and apply value transformations where enumerations differ between platforms.

Work Orders and Assets frequently carry attached photos, signed forms, and PDF documents. We migrate attachment URLs and metadata where Fame Service exposes a file API. If the attachment lives in a linked S3 bucket or internal document store, we replicate the file to the destination's storage and relink it to the target record.