Migrate from MotionOps to Freshsales

MotionOps stores all people in a single Contact object. During migration, FlitStack evaluates each contact's status: if the contact has an associated closed job or paid invoice, it routes to Freshsales Contact; if the contact has no job history, it routes to Freshsales Lead. This split preserves the MotionOps service relationship for existing customers while keeping prospects in the Lead object for Freshsales lead scoring.

MotionOps Company records map directly to Freshsales Accounts. Address, phone, and billing information migrate as Account fields. Multi-location companies in MotionOps collapse to a single Account with address data aggregated — individual locations are preserved as custom fields or address records if Freshsales multi-address configuration is enabled on the destination account.

MotionOps Jobs are the core operational record — each job has a status, assigned technician, scheduled time, address, line items, and cost breakdown. FlitStack translates each Job into a Freshsales Deal, mapping job name to Deal name, total job value to Deal amount, and job status to Deal stage. Unmapped fields like estimated hours, actual hours, and material cost become custom fields on the Deal record.

MotionOps Jobs contain one or more Work Orders, each with its own line items, labor rate, and material cost. FlitStack merges work order line items into the target Deal's product catalog — each work order becomes a product entry on the Deal. When the job has no product catalog equivalent in Freshsales, the line item data merges into a custom JSON or text field on the Deal record.

MotionOps proposals with accepted status convert to Deals with an 'Accepted Proposal' custom stage. Proposals in draft or sent status migrate as Deals in a 'Proposal' stage that maps to Freshsales pipeline stage values. Rejected proposals do not migrate as Deals — they are preserved as notes on the linked Account or Contact record.

Freshsales does not have a native invoice object. MotionOps invoice records — including invoice number, status (paid/unpaid/overdue), amount, and QuickBooks sync status — are preserved as a custom field group on the linked Account and Deal. Invoice history is not stored as a transactional object in Freshsales and must be reconciled in an accounting system post-migration.

MotionOps appointments (scheduled jobs with technician assignment and time windows) map to Freshsales Events with the original start/end time, assigned user (resolved by email), and address preserved. Appointments without a time block map as Tasks with the technician assigned as the task owner. Full route and optimization data does not have a Freshsales equivalent and is stored as a note attachment.

MotionOps stores team members with roles (technician, admin, manager), skill sets, and contact information. FlitStack resolves each member by email against Freshsales users — matched users receive record ownership. Unmatched members are flagged as 'Inactive owners' and records are reassigned to a designated fallback user. Skill and role data migrates to Freshsales user custom fields.

MotionOps time entries linked to a job migrate as task records attached to the corresponding Deal, with hours logged as a custom field. Standalone time entries not linked to a job (overhead hours) are stored as notes on the related Contact or Account. Billable vs. non-billable flag is preserved as a custom picklist field on the migrated task.

MotionOps custom fields on Jobs — such as job type, priority, equipment used, or special instructions — require corresponding custom fields in Freshsales on the Deal object. FlitStack creates these fields using the Freshsales custom field API (field type preserved: text, number, date, select, multi-select). Field-level permissions from Freshsales Enterprise tier are applied if the destination account uses field-level visibility rules.

MotionOps contact custom fields (certifications, trade licenses, insurance expiry) map to Freshsales Contact custom fields. FlitStack creates these during the schema setup phase. Contact-level custom fields are preserved on both Contact and Lead records during migration so that split routing does not lose data.

MotionOps file attachments on Jobs and Contacts (photos, signed documents, equipment images) are re-uploaded to Freshsales as file attachments on the corresponding Deal or Contact record. Freshsales applies a 25MB per-file size limit. Files exceeding this limit are split or linked via a URL reference stored in a custom field.