CRM migration

Migrate from Field Squared to Freshsales

Field-level mapping, validation, and rollback between Field Squared and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.

Field Squared logo

Field Squared

Source

Freshsales

Destination

Freshsales logo

Compatibility

92%

11 of 12

objects map 1:1 between Field Squared and Freshsales.

Complexity

BStandard

Timeline

5–10 business days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Field Squared and Freshsales occupy fundamentally different positions in the software stack. Field Squared is a field-service automation platform combining work-order management, enterprise asset management, and mobile workforce tracking. Freshsales is a Freshworks CRM focused on lead lifecycle, sales pipeline management, and account-based selling. The two platforms share few native object equivalents, which means a migration is less a direct port and more a strategic re-modeling of your data into CRM-native structures. We map Field Squared contacts to Freshsales Contacts and Leads, subcontractors to Accounts, work orders to Deals, and tasks or scheduled events to Freshsales Sales Activities. Field Squared's 30+ custom field types — including date fields, dropdowns, checkboxes, media attachments, and numeric fields — require individual Freshsales custom field creation and type-aware translation. Asset records that don't fit Freshsales' standard objects land in a custom Asset module we build as part of the migration schema. What does not migrate: Field Squared's workflow automation logic (routing rules, task-trigger sequences), dispatch scheduling constraints, GPS tracking data, service-contract pricing rules, and third-party integrations to accounting tools like QuickBooks or Paycom. These require Freshsales-side rebuilds. We deliver a workflow audit export from Field Squared so your admin can reference the original logic when configuring Freshsales automations. The migration runs via Field Squared's REST API (batch operations supported) and Freshsales' CRM Import API, with a 24–48 hour delta-pickup window at cutover to capture any in-flight work orders or updated contact records.

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

Field Squared logo

Field Squared

What's pushing teams away

  • Steep initial setup time due to extensive configuration options; organizations report significant investment during onboarding before realizing full value.
  • The learning curve for administrators managing custom fields, App Builder, and automation rules is steeper than simpler ticketing tools.
  • Reporting and analytics capabilities are functional but lack the depth of purpose-built BI tools, leading some customers to export data elsewhere for analysis.

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 Field Squared objects map to Freshsales

Each row shows how a Field Squared 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.

Field Squared

Contact

maps to

Freshsales

Contact / Lead

1:many
Fully supported

Field Squared contacts with an assigned account (subcontractor or customer) map to Freshsales Contacts. Unassigned contacts or leads in Field Squared route to Freshsales Leads. The split is configurable — your team chooses which contact status values map to Contact vs. Lead in Freshsales based on your sales-process definition.

Field Squared

Subcontractor

maps to

Freshsales

Account

1:1
Fully supported

Field Squared subcontractors are business entities that perform field work — they map directly to Freshsales Accounts. Subcontractor name maps to Account Name, and any address or contact information on the subcontractor record maps to the corresponding Account fields. Primary contact within the subcontractor links via Account Contact Relationship in Freshsales.

Field Squared

Work Order

maps to

Freshsales

Deal

1:1
Fully supported

Field Squared work orders are the core operational record — they map to Freshsales Deals. Work order name becomes Deal Name, work order status (e.g., Open, In Progress, Completed, Closed) maps to Freshsales deal stage values, and the estimated or actual duration maps to a custom field on the Deal. Revenue from the work order maps to Deal Amount.

Field Squared

Work Order Line Item / Material

maps to

Freshsales

Product

1:1
Fully supported

Field Squared line items and materials used in work orders map to Freshsales Products. Each unique material or service line becomes a Product record with its SKU, unit price, and description. During Deal creation, the line items attach as Product Items on the Freshsales Deal.

Field Squared

Asset

maps to

Freshsales

Custom Asset Module

1:1
Fully supported

Field Squared assets (equipment, vehicles, installed products under service contracts) have no native equivalent in Freshsales' standard CRM model. We create a Freshsales Custom Module named 'Assets' with custom fields for asset ID, location, status, make/model, and service contract linkage. This module associates to Accounts and Deals.

Field Squared

Location / Site

maps to

Freshsales

Account Address Fields

1:1
Fully supported

Field Squared locations or site records map to address fields on Freshsales Accounts. Multiple service locations associated with a single customer collapse to the primary Account address, with additional locations stored as Account Contact Relationships or address custom fields depending on your configuration.

Field Squared

Task (scheduled work)

maps to

Freshsales

Sales Activity (Task / Event)

1:1
Fully supported

Field Squared tasks with ScheduledStart and ScheduledEnd timestamps map to Freshsales Sales Activities. Tasks with a single scheduled time map to a Freshsales Task record; tasks spanning a time range map to an Event record. TaskType in Field Squared (e.g., Delivery, Installation, Inspection) maps to the Activity Type pick-list in Freshsales.

Field Squared

Document / Attachment

maps to

Freshsales

Freshsales Files

1:1
Fully supported

Field Squared Documents attached to work orders, tasks, or assets re-upload to Freshsales Files associated with the corresponding Deal, Contact, or custom Asset record. Files are re-hosted to Freshsales' own storage. Large file attachments may be subject to Freshsales file size limits per the destination plan.

Field Squared

Custom Fields (all types)

maps to

Freshsales

Freshsales Custom Fields

1:1
Fully supported

Field Squared's 30+ custom field types — including text, numeric, date, checkbox, dropdown, media, and multi-select — each require a corresponding Freshsales custom field. Text fields map directly. Numeric fields map to Freshsales number fields. Dropdowns and multi-select require value-by-value mapping where the pick-list options differ between platforms. Media fields require separate file migration and re-linkage.

Field Squared

User / Owner

maps to

Freshsales

Freshsales User

1:1
Fully supported

Field Squared users and assigned owners resolve to Freshsales users by email match. Unmatched owners are flagged before migration — you either provision them in Freshsales first or assign their records to a fallback user. The Owner field on Deals and Activities resolves via this match so all records land with the correct Freshsales owner from day one.

Field Squared

Service Contract

maps to

Freshsales

Deal / Custom Contract Module

1:1
Fully supported

Field Squared service contracts define recurring work, SLAs, and billing terms. Freshsales has no native service-contract object. We map active contracts to a Freshsales Deal with contract details stored in custom fields, or to a custom Contracts module if your plan supports it. SLA terms and pricing rules are preserved as text custom fields for reference.

Field Squared

Workflow / Automation

maps to

Freshsales

Freshsales Workflows

1:1
Fully supported

Field Squared workflow logic (routing rules, auto-assignment, status triggers, notification sequences) does not migrate. We export your workflow definitions as a structured JSON document so your Freshsales admin can reference the original rules when building Freshsales Workflows. Automations must be rebuilt — we do not offer automation migration as part of the data-only service.

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.

Field Squared logo

Field Squared gotchas

High

Automation Rules and Dashboard configurations lack public API access

Medium

No dedicated Customers API—contact data extracted from Work Orders

Low

Batch document migration requires array-based payload construction

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

  • Asset records have no native CRM home in Freshsales

    Field Squared's enterprise asset management module stores equipment records, service histories, and warranty data that have no equivalent in Freshsales' standard object model. Freshsales has no native Asset object — the standard workaround is to create a Custom Module named 'Assets' with custom fields for asset ID, status, location, make/model, and service contract linkage. This module does not appear in Freshsales' standard reporting paths and requires custom dashboard configuration to surface alongside Accounts and Deals. We create the schema as part of the migration plan, but your team needs to decide whether asset data should live alongside CRM records or in a separate tool.

  • Work order status values require Freshsales stage-value mapping before migration runs

    Field Squared work orders carry custom status values (e.g., Dispatched, En Route, On Site, Pending Parts, Closed — Invoice Sent) that don't map to Freshsales' default deal stage pick-list. Each Field Squared status must be mapped to a corresponding Freshsales deal stage before data loads, otherwise records land in an unmapped state and require manual correction. We deliver a status-mapping worksheet before the migration runs so your Freshsales admin can define the stage values and their probability weights in Salesforce Setup > Opportunity Stages before records land.

  • Custom field name matching is case-sensitive between Field Squared and Freshsales

    Freshsales' CRM Import API matches custom fields by exact name — a Field Squared custom field named 'Job Type' will not auto-map to a Freshsales custom field named 'Job type'. This is particularly risky because Field Squared's App Builder allows spaces in custom field names while Freshsales' Admin > Custom Fields interface may normalize them differently on save. We pre-validate field names before migration and flag any case or spacing mismatches so you can correct the Freshsales custom field names before the import runs.

  • Field Squared's 25,000-record instant import limit applies per Freshsales batch

    Freshsales' Admin > CRM Data Import supports instantaneous imports up to 25,000 records per batch. Field Squared accounts with large work order histories or high-volume task logs routinely exceed this threshold. Records above 25,000 must be submitted as an off-peak batch request, which Freshworks processes within 1–2 business days. We partition large migrations into sub-25k batches and sequence them so the most business-critical records (open deals, active contacts) import first, with historical records loading in a secondary pass.

  • Workflow and automation logic is not data — it requires a manual rebuild

    Field Squared's workflow configuration defines how work orders route to technicians based on location, skill, or availability, and how status transitions trigger notifications or field updates. This logic lives in Field Squared's workflow engine and does not export as data. Freshsales' Workflows (auto-assignment rules, field-update triggers) and Sales Sequences handle similar functions but use a different configuration model. We export your Field Squared workflow definitions as a structured JSON reference document so your Freshsales admin can rebuild the routing logic in Freshsales Workflows. The rebuild is a configuration task, not a data migration task.

Migration approach

Six steps for a successful Field Squared to Freshsales data migration

  1. Audit Field Squared data model and export via REST API

    We connect to Field Squared's REST API using your account credentials and run a full data audit — counting contacts, subcontractors, work orders, assets, tasks, and custom fields across all modules. We identify custom field types, pick-list values, and any record relationships that need resolution during migration. The audit output is a schema map comparing every Field Squared object to its Freshsales target, with custom field creation instructions for each.

  2. Create Freshsales custom fields and Asset module schema

    Before any data moves, we create all required Freshsales custom fields: custom fields on Contacts, Accounts, Deals, and Sales Activities matching every Field Squared custom field name and type. We also create the Asset custom module with its field set. You can either create these yourself from our schema plan or authorize us to create them via Freshsales Admin. Freshsales must be on a plan that supports the required custom field counts — Enterprise plan is recommended for migrations exceeding 20 custom fields.

  3. Map and partition data for Freshsales import batch limits

    We partition the migration into Freshsales-compatible batches — each capped at 25,000 records per import run. Active contacts, open work orders, and current subcontractors import in the first batch. Historical tasks, completed work orders, and attachments load in subsequent batches. We generate the Freshsales CRM Data Import CSV files with correct field headers, pick-list values, and owner email resolution for each batch. Owner resolution runs first: Field Squared owner emails are matched against Freshsales users, with unmatched owners flagged for you to provision or assign to a fallback.

  4. Run a sample migration with field-level diff

    A representative sample — typically 200–500 records covering a mix of contacts, accounts, work orders, tasks, and asset records — runs first against your live Freshsales instance. We generate a field-level diff report showing every mapped value, transformed field, and any unmapped or truncated records. You review the diff and approve before the full run commits. This is the validation gate: it catches custom field name mismatches, value-mapping gaps, and owner resolution failures before they affect your full dataset.

  5. Execute full migration with delta-pickup cutover

    Full migration runs against Freshsales using the approved field mapping and batch sequence. A delta-pickup window opens at cutover — typically 24–48 hours — during which any records created or updated in Field Squared after the migration snapshot are captured and loaded into Freshsales. Our audit log records every record touched. If reconciliation fails, one-click rollback reverts the Freshsales instance to its pre-migration state. After rollback confirmation, your team can re-run the migration with corrected mapping.

Platform deep dives

Context on both ends of the pair

Field Squared logo

Field Squared

Source

Strengths

  • Combines FSM, EAM, and mobile workforce management in a single configurable platform.
  • RESTful API supports single and batch operations with authenticated HTTP headers.
  • Highly extensible via App Builder and 30+ custom field types for industry-specific data modeling.
  • Per-user tiered pricing ($70–$125/month) allows selective feature access without full platform licensing.
  • Real-time dispatch and GPS tracking capabilities for distributed field operations.

Weaknesses

  • No public API for Automation Rules or Dashboard/report definitions—these must be manually recreated in the destination.
  • Extensive configuration requirements result in a steep learning curve during initial setup.
  • Customer data lacks a dedicated API endpoint, requiring extraction from Work Order associations.
  • Limited documented audit trail or bulk export tooling outside the core API.
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 Field Squared 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

    Field Squared: Not publicly documented.

  • Data volume sensitivity

    A

    Field Squared exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Field Squared 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 Field Squared to Freshsales data migrations

Answers to the questions buyers ask most during Field Squared to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Field Squared to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

A standard Field Squared to Freshsales migration for under 25,000 total records completes in 5–10 business days: one week for data audit, schema setup, and sample migration; one to three days for the full run. Migrations exceeding 25,000 records — common when work order histories span multiple years — extend to 3–6 weeks because they require Freshsales' off-peak batch import process and multi-batch sequencing. The longest single step is typically Freshsales custom field creation and schema validation before data loads.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Field Squared.
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