CRM migration

Migrate from Novo Work Order to Freshsales

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 logo

Novo Work Order

Source

Freshsales

Destination

Freshsales logo

Compatibility

92%

11 of 12

objects map 1:1 between Novo Work Order and Freshsales.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Novo Work Order logo

Novo Work Order

What's pushing teams away

  • 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.

Choosing

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How Novo Work Order objects map to Freshsales

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

maps to

Freshsales

Deal

1:1
Fully supported

Novo 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

maps to

Freshsales

Deal Stage

1:1
Fully supported

Novo'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

maps to

Freshsales

Account

1:1
Fully supported

Novo 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

maps to

Freshsales

Account Custom Field + Territory

1:1
Fully supported

Novo 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

maps to

Freshsales

Lead / Contact

1:many
Fully supported

Novo 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

maps to

Freshsales

User

1:1
Fully supported

Novo 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

maps to

Freshsales

Deal Custom Field (URL) / Freshsales Files

1:1
Fully supported

Novo 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

maps to

Freshsales

Deal Activity (Task / Note)

1:1
Fully supported

Novo 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)

maps to

Freshsales

Custom Fields (Deal)

1:1
Fully supported

Novo 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

maps to

Freshsales

Custom Object / Task

1:1
Fully supported

Novo 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

maps to

Freshsales

Territory / Custom Field

1:1
Fully supported

Novo 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)

maps to

Freshsales

Lead

1:1
Fully supported

Citizen-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.

Gotchas + challenges

What specifically takes care here

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 logo

Novo Work Order gotchas

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

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Work orders have no native Freshsales object — they become deals with custom fields

    Freshsales is a CRM built around leads, contacts, accounts, and deals. Novo Work Order records do not map to any standard Freshsales object because Freshsales has no concept of work orders, technicians, labor hours, or permit numbers. FlitStack AI represents every Novo work order as a Freshsales Deal with priority, type, status, labor hours, and parts cost stored as custom fields on the deal. The deal Owner maps to the assigned technician via email match. Freshsales deal records do not support scheduling windows or time-slot assignment natively — those must be rebuilt using Freshsales Tasks with due dates or a third-party scheduling integration after migration.

  • Asset hierarchies flatten in Freshsales — parent-child relationships require custom field reconstruction

    Novo Work Order supports nested asset hierarchies (parent asset → child asset → component) which is a first-class feature in the platform. Freshsales Accounts have a flat structure — there is no native parent-child account model in Freshsales CRM. When a Novo asset has a parent_asset_id, FlitStack AI stores the parent asset ID as a custom text field (Parent_Asset_ID__c) on the child account record. Rebuilding the hierarchy visualization requires either a custom Freshsales app built on the app SDK or a third-party asset-visualization integration. This limitation is inherent to Freshsales' object model and affects any migration where asset sub-assets are significant.

  • Novo department routing has no Freshsales equivalent — territory management must be configured post-migration

    Novo Work Order routes work orders to departments and divisions using type-based and location-based auto-assignment rules. Freshsales does not have a department concept — it uses Territory Management to assign records to users based on geography or record attributes. During migration, the Novo department name is stored as a custom pick-list field on both Accounts and Deals (Department__c). After migration, your Freshsales admin must create territories in Admin Settings → Territories and configure territory assignment rules that reference this field. Without this step, department-level routing does not function in Freshsales.

  • File attachments migrate as URL references, not as re-uploaded files

    Novo stores file attachments (images, PDFs, inspection reports) linked to work orders and assets. Freshsales Files are stored within Freshsales' own file storage system and have a different URL structure. FlitStack AI migrates file attachment metadata — original filename, file type, and the source URL path — as a custom multi-line text field on the corresponding Deal or Account. The actual files are not re-uploaded to Freshsales Files automatically because the source URL paths expire after the Novo account is deactivated. If file re-upload is required, a separate file-migration step must be scoped post-migration with URL remapping.

  • Preventive maintenance schedules are scheduling logic, not data — they cannot migrate

    Novo preventive maintenance schedules are automated scheduling constructs that generate work orders at configured intervals (e.g., generate inspection work order every 90 days for asset X). Freshsales has no scheduling engine for generating recurring work orders — it is a CRM, not a CMMS. The PM schedule metadata (frequency, interval, last-completed date, linked asset) migrates as reference fields on the Account record, but the automation logic that generates recurring work orders does not exist in Freshsales. FlitStack AI exports the PM schedule definitions as a structured document that your team or a Freshsales partner can use to rebuild PM automation using Freshsales workflows or a connected scheduling tool.

Migration approach

Six steps for a successful Novo Work Order to Freshsales data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Novo Work Order logo

Novo Work Order

Source

Strengths

  • Links work orders directly to physical assets and equipment for full maintenance history
  • Multi-department routing handles municipal organizational structures out of the box
  • Preventative maintenance scheduling reduces reactive repairs on infrastructure
  • Custom fields, forms, and workflows adapt to municipal compliance and reporting requirements
  • Mobile app allows field technicians to update work order status and log labor from the job site

Weaknesses

  • No public API documented — migration depends on built-in export functions and support coordination
  • Pricing is opaque — no self-service quotes, free tier, or published per-seat cost
  • Designed for municipal government use cases — lacks commercial field service contract and SLA features
  • Limited third-party integrations compared to modern FSM platforms
  • Reporting and analytics are built-in dashboards rather than a queryable data warehouse
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Novo Work Order and Freshsales.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Novo Work Order: Not publicly documented.

  • Data volume sensitivity

    B

    Novo Work Order doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Novo Work Order to Freshsales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Novo Work Order to Freshsales data migrations

Answers to the questions buyers ask most during Novo Work Order to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Novo Work Order to Freshsales migrations complete in 48–72 hours for data volumes under 25,000 records. Larger setups with 100,000+ records, complex multi-department asset hierarchies, or extensive custom fields extend to 5–7 days. The longest step is schema setup — creating custom fields, configuring deal stages, and pre-creating Freshsales users — which runs in parallel with migration planning before any data moves. The delta-pickup window adds 24–48 hours to the final cutover but does not block your team from working in Novo during that period.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Novo Work Order.
Land in Freshsales, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day