Migrate your Novo Work Order data
Cloud-based work order and asset management platform built for municipal government operations. We help teams extract data from it when they outgrow it or switch platforms.
In its favor
Why people choose Novo Work Order
The signal that keeps Novo Work Order on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Auto-routing of requests submitted via email, web portal, or mobile app to the appropriate department reduces dispatcher workload.
Customisable fields, forms, record lists, email templates, workflows, and permissions let small operations adapt the data model without engineering work.
Multi-department permission model lets municipalities and facilities teams segment data and limit cross-department access from one tenant.
Cloud-based with mobile support gives field staff access without IT-managed VPN setup.
Customer service team praised in reviews as 'great, always extremely helpful, knowledgeable, professional, and friendly.'
Search engine across the platform is described in reviews as 'horrible' — locating older work orders or asset records can require multiple filter passes.
Some features are not intuitive and require training; reviewers note a documented learning curve.
Report writing is difficult to use according to reviewer feedback — operations needing rich custom reporting often supplement with external BI.
Public pricing is limited to the ShareNet Basic Edition at $25/user/month (annual, 3-user minimum); higher tiers are quoted by sales.
Vendor scale is small relative to FSM / CMMS leaders like Fiix, UpKeep, or ServiceChannel — partner ecosystem and community resources are thinner.
Reasons to switch
Why people leave Novo Work Order
The recurring reasons buyers give for replacing Novo Work Order. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Novo Work Order fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Novo Work Order pricing overview
Novo Solutions does not publish pricing publicly. All accounts are sold through a custom sales-assisted process, with quotes based on the number of departments, total assets, and users. There is no free tier, self-service trial, or per-seat pricing listed on the website. Prospective customers must contact Novo Solutions directly or request a quote through a reseller channel.
ShareNet Basic
Tier 1 of 2
$25/user/month (annual; 3-user minimum)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Novo Work Order's schedule — see our quote-based pricing →
What gets migrated
Novo Work Order object support
Object-by-object support for Novo Work Order migrations. Per-pair details surface during scoping.
Work Orders
Mapping requiredThe core object. Exports include WO number, status, priority, assigned technician, department, labor hours, parts used, and timestamps. Status values and priority scales vary by municipal configuration — we map these to the destination's pipeline stages on a per-customer basis.
Assets and Equipment
Mapping requiredPhysical infrastructure assets (vehicles, meters, facilities, utility equipment) linked to work orders. The asset hierarchy can be deep — parent/child relationships and location fields need explicit mapping during import to preserve the maintenance history context.
Preventative Maintenance Schedules
Mapping requiredRecurring maintenance tasks tied to assets. The recurrence rules (daily, weekly, calendar-based, meter-based) export but may not map directly to the destination's scheduling model. We translate these into the destination's equivalent recurrence format or convert them to individual scheduled work orders.
Departments
Mapping requiredMunicipal departments (Public Works, Water, Parks, Utilities) used for routing and permissions. Department names and hierarchies are not standardized across Novo Solutions tenants. We extract the full department tree and map each to the destination's organizational unit structure.
Requests
Mapping requiredIncoming service requests from the web portal, email, or mobile app intake forms. May include requestor contact information, source channel, and initial description. We extract these as Work Order records or as linked request objects depending on the destination schema.
Custom Fields
Mapping requiredMunicipal-specific fields such as Council District, Permit Number, Regulatory Compliance Flag, or Inspection Result. These export as named columns in the work order dump. We preserve field names, data types, and picklist values for reconstruction in the destination.
Workflows and Forms
Mapping requiredApproval chains, routing rules, and intake forms configured in Novo Solutions. These are not structured data exports — they require manual reconstruction in the target system. We document the current workflow logic during discovery so the destination can be configured to match.
Users and Permissions
Mapping requiredTechnicians, supervisors, department heads, and read-only users. Role names (Dispatcher, Field Tech, Admin) vary by tenant configuration. We extract the user list, their assigned departments, and role assignments to recreate the permission structure in the destination.
Attachments
Mapping requiredPhotos, inspection documents, and signed forms attached to work orders or assets. These export as a separate file bundle with reference IDs linking them back to the parent record. We re-associate the file bundle with the imported records during the post-import verification phase.
Inventory and Parts
Mapping requiredParts catalog, stock levels, and parts usage logged against work orders. Parts lists and on-hand quantities export separately from work orders. We handle these as a distinct import pass, linking parts usage records back to their originating work orders by WO number.
| Object | Support | Notes |
|---|---|---|
| Work Orders | Mapping required | The core object. Exports include WO number, status, priority, assigned technician, department, labor hours, parts used, and timestamps. Status values and priority scales vary by municipal configuration — we map these to the destination's pipeline stages on a per-customer basis. |
| Assets and Equipment | Mapping required | Physical infrastructure assets (vehicles, meters, facilities, utility equipment) linked to work orders. The asset hierarchy can be deep — parent/child relationships and location fields need explicit mapping during import to preserve the maintenance history context. |
| Preventative Maintenance Schedules | Mapping required | Recurring maintenance tasks tied to assets. The recurrence rules (daily, weekly, calendar-based, meter-based) export but may not map directly to the destination's scheduling model. We translate these into the destination's equivalent recurrence format or convert them to individual scheduled work orders. |
| Departments | Mapping required | Municipal departments (Public Works, Water, Parks, Utilities) used for routing and permissions. Department names and hierarchies are not standardized across Novo Solutions tenants. We extract the full department tree and map each to the destination's organizational unit structure. |
| Requests | Mapping required | Incoming service requests from the web portal, email, or mobile app intake forms. May include requestor contact information, source channel, and initial description. We extract these as Work Order records or as linked request objects depending on the destination schema. |
| Custom Fields | Mapping required | Municipal-specific fields such as Council District, Permit Number, Regulatory Compliance Flag, or Inspection Result. These export as named columns in the work order dump. We preserve field names, data types, and picklist values for reconstruction in the destination. |
| Workflows and Forms | Mapping required | Approval chains, routing rules, and intake forms configured in Novo Solutions. These are not structured data exports — they require manual reconstruction in the target system. We document the current workflow logic during discovery so the destination can be configured to match. |
| Users and Permissions | Mapping required | Technicians, supervisors, department heads, and read-only users. Role names (Dispatcher, Field Tech, Admin) vary by tenant configuration. We extract the user list, their assigned departments, and role assignments to recreate the permission structure in the destination. |
| Attachments | Mapping required | Photos, inspection documents, and signed forms attached to work orders or assets. These export as a separate file bundle with reference IDs linking them back to the parent record. We re-associate the file bundle with the imported records during the post-import verification phase. |
| Inventory and Parts | Mapping required | Parts catalog, stock levels, and parts usage logged against work orders. Parts lists and on-hand quantities export separately from work orders. We handle these as a distinct import pass, linking parts usage records back to their originating work orders by WO number. |
Gotchas
What to watch for in Novo Work Order migrations
Issues we've hit on past Novo Work Order migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| High | No public API forces migration via built-in exports |
| Medium | Pricing opacity complicates budget planning |
| Medium | Municipal-specific custom fields need careful schema mapping |
| Low | Preventative maintenance recurrence rules vary by configuration |
Leaving Novo Work Order?
Where Novo Work Order customers move next
12 destinations Novo Work Order can migrate to.
How a Novo Work Order migration works
Four steps, Novo Work Order-specific
Connect
Not publicly documented into Novo Work Order. Scopes limited to read-only on the data we move.
Map
We translate Novo Work Order-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Novo Work Order quirks before production.
Migrate
Full migration with Novo Work Order rate-limit handling. Rollback available throughout.
FAQ
Novo Work Order migration FAQ
Answers to the questions buyers ask most during Novo Work Order migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Novo Work Order migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Novo Work Order.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Novo Work Order setup and destination — written quote back within a business day.