Migrate from MotionOps to Zoho CRM

MotionOps contacts with an email address map directly to Zoho CRM Contacts. The contact's name, phone, email, and address fields transfer as-is. Contacts without email route to Zoho Leads instead, since Zoho requires a unique email for Contact records. Owner resolution happens by email match against Zoho users.

Contacts in MotionOps that lack an email address cannot become Zoho CRM Contacts (Zoho requires email for Contact records). These route to Zoho Leads, which accept records without email. The original MotionOps contact ID is preserved as Source_System_ID__c on the Lead for traceability.

MotionOps companies map to Zoho CRM Accounts — the Account Name, website, industry, phone, and billing address transfer directly. Company hierarchies (parent/child) map to Zoho's Parent Account lookup field. Multi-company contacts in MotionOps (one contact linked to multiple companies) resolve to a primary Account with additional relationships surfaced as Contacts.

MotionOps jobs are the primary work unit and map to Zoho CRM Deals. The job name becomes the Deal name, the job amount becomes the Deal amount, and the job status maps to a Zoho pipeline stage. Job creation date and last-modified date are preserved as custom fields since Zoho Deal fields have limited historical tracking.

MotionOps job line items (materials, labor, services) transfer as Zoho Deal Products if your Zoho edition includes the Products module. Each line item becomes a Deal Product entry with product name, quantity, unit price, and total. If the Products module is not available in your Zoho edition, line items serialize into a custom multi-line text field for reference.

MotionOps job statuses (New, Scheduled, In Progress, Completed, Cancelled, On Hold) map to Zoho CRM Deal Stage values via value-by-value mapping. Each MotionOps status value is assigned to a corresponding Zoho stage. Probability and forecast category are re-applied based on Zoho's stage configuration after mapping.

MotionOps custom fields (text, select, multiSelect, date, number, phone, email, checkbox, person, multiPerson, url, relatedTo) require corresponding custom fields in Zoho CRM. Each MotionOps custom field is created in Zoho with the matching data type before migration. Person and multiPerson fields become Zoho User lookups; relatedTo fields become Zoho Lookup fields. Select and multiSelect fields require value mapping for picklist options.

MotionOps notes attached to contacts, companies, or jobs migrate to Zoho CRM Notes. The note body, parent record (contact/company/job), creation date, and note owner transfer. Rich-text formatting is preserved where possible. Notes on jobs that become Deals link to the corresponding Zoho Deal record.

File attachments on MotionOps records (photos, documents, PDFs) are downloaded and re-uploaded to Zoho CRM Attachments linked to the corresponding record. File size limits per Zoho edition apply. Inline images embedded in notes are extracted, downloaded separately, and re-hosted as Zoho FileAttachments to maintain visibility within the record.

MotionOps users and job assignees resolve by email match against Zoho CRM users. Unmatched users are flagged before migration — your team either creates Zoho user accounts first or assigns records to a fallback owner. Technician names from MotionOps without Zoho accounts become a custom text field on the Deal for reference.

MotionOps scheduling data (appointment times, technician routes, schedule slots) has no direct Zoho CRM equivalent. Appointments migrate as Zoho CRM Tasks with subject, start date, and assigned user. Route and dispatch data is preserved as a JSON-formatted custom long-text field on the Deal for historical reference — this cannot be displayed as a calendar view in standard Zoho CRM.

MotionOps invoices and payment records (Stripe transaction IDs, payment status, amounts paid) do not migrate to Zoho CRM as native records. Invoice PDFs are attached to the corresponding Deal record as reference attachments. Full financial history requires migration to Zoho Books or QuickBooks separately from the CRM migration.