CRM migration
Field-level mapping, validation, and rollback between Field Squared and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Field Squared
Source
Freshsales
Destination
Compatibility
11 of 12
objects map 1:1 between Field Squared and Freshsales.
Complexity
BStandard
Timeline
5–10 business days
Overview
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.
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 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
Freshsales
Contact / Lead
1:manyField 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
Freshsales
Account
1:1Field 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
Freshsales
Deal
1:1Field 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
Freshsales
Product
1:1Field 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
Freshsales
Custom Asset Module
1:1Field 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
Freshsales
Account Address Fields
1:1Field 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)
Freshsales
Sales Activity (Task / Event)
1:1Field 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
Freshsales
Freshsales Files
1:1Field 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)
Freshsales
Freshsales Custom Fields
1:1Field 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
Freshsales
Freshsales User
1:1Field 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
Freshsales
Deal / Custom Contract Module
1:1Field 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
Freshsales
Freshsales Workflows
1:1Field 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.
| Field Squared | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Contact / Lead1:many | Fully supported | |
| Subcontractor | Account1:1 | Fully supported | |
| Work Order | Deal1:1 | Fully supported | |
| Work Order Line Item / Material | Product1:1 | Fully supported | |
| Asset | Custom Asset Module1:1 | Fully supported | |
| Location / Site | Account Address Fields1:1 | Fully supported | |
| Task (scheduled work) | Sales Activity (Task / Event)1:1 | Fully supported | |
| Document / Attachment | Freshsales Files1:1 | Fully supported | |
| Custom Fields (all types) | Freshsales Custom Fields1:1 | Fully supported | |
| User / Owner | Freshsales User1:1 | Fully supported | |
| Service Contract | Deal / Custom Contract Module1:1 | Fully supported | |
| Workflow / Automation | Freshsales Workflows1: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.
Field Squared gotchas
Automation Rules and Dashboard configurations lack public API access
No dedicated Customers API—contact data extracted from Work Orders
Batch document migration requires array-based payload construction
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
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.
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.
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.
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.
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
Field Squared
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 Field Squared 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
Field Squared: Not publicly documented.
Data volume sensitivity
Field Squared exposes a bulk API — large-volume migrations stream efficiently.
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 Field Squared to Freshsales migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Field Squared
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.