CRM migration
Field-level mapping, validation, and rollback between Novo Work Order and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Novo Work Order
Source
Freshsales
Destination
Compatibility
11 of 12
objects map 1:1 between Novo Work Order and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
Novo Work Order is a field-service and work-order management platform built for public-works, facilities, and utilities teams — it organizes assets, work orders, preventive maintenance schedules, and department-level request routing. Freshsales is a CRM platform structured around leads, contacts, accounts, and deals with pipeline stages and lifecycle stages for contact progression. These platforms share no native object equivalency: work orders do not exist in Freshsales natively, assets are not a standard Freshsales object, and Novo's scheduling and technician-assignment model has no CRM analogue. FlitStack AI handles this structural gap by converting Novo work orders to Freshsales deals, Novo assets to Freshsales accounts, and service-request contacts to Freshsales leads or contacts based on email address. Custom fields, attachment URLs, and status-history logs migrate as custom fields on the corresponding Freshsales object. Workflows, automations, department routing rules, and preventive-maintenance schedules do not transfer — Freshsales does not execute those logic types, and they must be rebuilt using Freshsales workflows and territory assignment rules post-migration. The migration uses Novo's built-in bulk export to produce structured CSVs, maps those to Freshsales API-compatible payloads, and loads through Freshsales' import API with field validation.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Novo Work Order object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Novo Work Order
Work Order
Freshsales
Deal
1:1Novo Work Orders become Freshsales Deals. Work order title maps to Deal Name, amount can be derived from labor hours × rate or parts cost if those fields are populated in Novo. Priority, type, and status migrate as custom pick-list fields on the deal. The deal Owner maps to the assigned technician via email match.
Novo Work Order
Work Order Status
Freshsales
Deal Stage
1:1Novo's Open / Assigned / In Progress / On Hold / Completed / Cancelled status values map value-by-value to Freshsales Deal Stage pick-list entries. Each Novo status gets a corresponding stage name chosen at migration planning time — probability and forecast category re-applied in Freshsales after migration.
Novo Work Order
Asset
Freshsales
Account
1:1Novo Assets map directly to Freshsales Accounts — asset name becomes Account Name, asset location maps to Account Address, and asset type can become Industry or a custom Account field. Asset condition ratings and meter readings store as custom number fields on the account.
Novo Work Order
Asset Location / Department
Freshsales
Account Custom Field + Territory
1:1Novo asset location (street address, GPS coordinates, department) stores as custom address and text fields on the Freshsales Account. Department-level grouping does not map to a native Freshsales concept — Territory Management in Freshsales handles geographic routing post-migration after accounts are loaded.
Novo Work Order
Service Request
Freshsales
Lead / Contact
1:manyNovo service requests submitted by citizens or internal staff with no existing contact record in Novo become Freshsales Leads. Requests linked to a contact email that already exists in Novo's contact list become Freshsales Contacts. The split is determined by whether a valid email address exists on the source request record.
Novo Work Order
Technician / Staff
Freshsales
User
1:1Novo technician and staff user accounts resolve to Freshsales Users by email address match. Unmatched Novo users are flagged before migration — your team either creates Freshsales user accounts first or assigns those work orders to a fallback Freshsales user owner.
Novo Work Order
Work Order Attachments / Files
Freshsales
Deal Custom Field (URL) / Freshsales Files
1:1Novo file attachments on work orders do not have a native Freshsales equivalent. We migrate attachment URLs as a custom multi-line text field on the deal referencing the original URL path. If file re-upload to Freshsales Files is requested, the migration plan includes a separate file-migration step with URL re-mapping after the primary record load.
Novo Work Order
Work Order Notes / Activity Log
Freshsales
Deal Activity (Task / Note)
1:1Novo work order activity logs, internal notes, and status-change history map to Freshsales Tasks with Subject describing the activity type and Description containing the full log text. Original timestamps and technician-owner information are preserved on each task, maintaining complete service history traceability for audit compliance and future customer interactions.
Novo Work Order
Custom Fields (Work Order)
Freshsales
Custom Fields (Deal)
1:1Novo custom fields on work orders (e.g., inspection results, permit numbers, failure codes) require corresponding custom fields to be created in Freshsales before migration. Field type mapping is performed per custom field — text → text, number → number, pick-list → pick-list with value-by-value mapping for each pick-list option.
Novo Work Order
Preventive Maintenance Schedule
Freshsales
Custom Object / Task
1:1Novo preventive maintenance schedules are a scheduling construct with no Freshsales CRM equivalent. PM frequency, interval, and last-completed data migrate as custom fields on the linked Account or Deal for reference. Scheduling automation must be rebuilt using Freshsales workflows or a third-party scheduling integration post-migration.
Novo Work Order
Department / Division
Freshsales
Territory / Custom Field
1:1Novo department and division records do not have a direct Freshsales equivalent. Department name migrates as a custom pick-list field on Accounts and Deals. For organizations that rely on department-level routing, Freshsales Territory Management must be configured post-migration and territory assignment rules rebuilt.
Novo Work Order
Request (Citizen Portal)
Freshsales
Lead
1:1Citizen-submitted requests from Novo's public portal map to Freshsales Leads with the request title as Lead Name and the request description in the Lead Description field. Request priority maps to the custom priority field on the lead. No account association exists in this flow — the lead is created standalone and linked to an account if a contact match is found.
| Novo Work Order | Freshsales | Compatibility | |
|---|---|---|---|
| Work Order | Deal1:1 | Fully supported | |
| Work Order Status | Deal Stage1:1 | Fully supported | |
| Asset | Account1:1 | Fully supported | |
| Asset Location / Department | Account Custom Field + Territory1:1 | Fully supported | |
| Service Request | Lead / Contact1:many | Fully supported | |
| Technician / Staff | User1:1 | Fully supported | |
| Work Order Attachments / Files | Deal Custom Field (URL) / Freshsales Files1:1 | Fully supported | |
| Work Order Notes / Activity Log | Deal Activity (Task / Note)1:1 | Fully supported | |
| Custom Fields (Work Order) | Custom Fields (Deal)1:1 | Fully supported | |
| Preventive Maintenance Schedule | Custom Object / Task1:1 | Fully supported | |
| Department / Division | Territory / Custom Field1:1 | Fully supported | |
| Request (Citizen Portal) | Lead1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Novo Work Order gotchas
No public API forces migration via built-in exports
Pricing opacity complicates budget planning
Municipal-specific custom fields need careful schema mapping
Preventative maintenance recurrence rules vary by configuration
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Inventory Novo data and design Freshsales schema
FlitStack AI extracts a full data inventory from Novo Work Order using its built-in bulk export, cataloguing every work order, asset, contact, department, and custom field. We then map each Novo object to its Freshsales equivalent — work orders to Deals, assets to Accounts, requests to Leads or Contacts — and identify all custom fields that need creation in Freshsales before any record loads. We deliver a Freshsales setup plan listing every custom field to create, the Deal Stage values to configure per pipeline, and any territory or user accounts to pre-create so Freshsales is schema-ready before data moves.
Create Freshsales custom fields and resolve user accounts
Your Freshsales admin (or our team acting with admin credentials) creates the custom fields identified in the schema plan — Priority__c, Type__c, Department__c, Labor_Hours__c, Parts_Cost__c, Condition_Rating__c, and others — on the Deal and Account objects in Freshsales Admin Settings. Simultaneously, Novo technician and staff accounts are resolved by email match against Freshsales Users. Any Novo user without a corresponding Freshsales account is flagged so your team can create those users before the migration run. This step prevents OwnerId lookup failures during the deal load.
Load assets and accounts before work orders and deals
Freshsales requires AccountId to exist before a Deal record can reference it — similar to how Salesforce requires accounts before contacts. FlitStack AI sequences the migration in dependency order: first Accounts (from Novo Assets), then Leads and Contacts (from Novo Requests and technician contacts), then Deals (from Novo Work Orders) with AccountId resolved from the account load step. Activities and notes are loaded after their parent records. This sequencing ensures foreign-key integrity throughout the migration and prevents Freshsales import validation errors from missing lookup targets.
Run sample migration with field-level diff
A representative sample — typically 100–500 records spanning work orders across different statuses and departments, assets from multiple locations, and a mix of request types — migrates into Freshsales before the full run. FlitStack AI generates a field-level diff comparing the source Novo values against the destination Freshsales field values, verifying that status value mappings are correct, custom fields populated, owner resolution working, and timestamps preserved. You review the sample diff in a shared spreadsheet and approve the mapping logic before the full migration commits.
Execute full migration with delta-pickup cutover window
The full data migration runs against Freshsales using Freshsales' import API, loading all work orders, assets, requests, contacts, and activities in sequenced dependency order. During the cutover window (typically 24–48 hours), FlitStack AI captures any records created or modified in Novo Work Order after the initial extraction — delta records are merged into Freshsales before the go-live cutover. All operations are logged to an audit trail, and a one-click rollback to the pre-migration state is available if reconciliation uncovers data integrity issues.
Platform deep dives
Novo Work Order
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Novo Work Order and Freshsales.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Novo Work Order: Not publicly documented.
Data volume sensitivity
Novo Work Order doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Novo Work Order to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Novo Work Order to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Novo Work Order
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.