Migrate from ForceManager CRM to Freshsales

ForceManager Company records map to Freshsales Account. Standard fields (name, type, rating, address, responsible person) map to Freshsales Account fields. The z_ prefixed custom fields are extracted from the Fields endpoint, the prefix is stripped, and fields are recreated as native Freshsales custom fields with human-readable labels before import. Owner assignment resolves via email match against Freshsales User records.

ForceManager Contact records map to Freshsales Contact. Each Contact is linked to its parent Account via the Account lookup. Custom fields with z_ prefix follow the same label-extraction and recreation process as on Account. Contact owner resolves by email match. ForceManager does not have a separate Lead object, so all contacts land as Freshsales Contacts rather than requiring a Lead-Contact split unless the customer wants to segment by qualification status.

ForceManager Opportunities map to Freshsales Deals. The opportunity stage name maps to Freshsales Deal stage, and pipeline assignment maps to a Freshsales Deal pipeline that we configure before migration. Custom opportunity fields (z_ prefixed) migrate as described above. Closed-Lost and Closed-Won dates and amounts preserve in Freshsales Deal fields.

ForceManager Activities (calls, meetings, field interactions) map to Freshsales Tasks. Activity type, date, duration, and linked Contact and Company are preserved. GPS coordinates and location data from ForceManager field visits are appended as a text note within the Task body to preserve location context since Freshsales does not have a native GPS field type.

ForceManager calendar Events map to Freshsales Tasks with activity_type set to Meeting. Start time, end time, and attendee list transfer. Location (including GPS coordinates from ForceManager) appends to the Task notes field. Event recurrence patterns are not preserved; recurring events are documented for manual recreation in Freshsales Calendar.

ForceManager Tasks map to Freshsales Tasks with status (open/completed), due date, priority, and assignee preserved. Task owner resolves via email match. Completion timestamps transfer where available.

ForceManager Sales Order and Sales Order Line entities map to Freshsales Deals with associated Products. Order header fields (order date, status, total amount) map to Deal custom fields. Line items map to Freshsales Products with pricing. If the destination Freshsales plan lacks a formal Order object, order data consolidates into the Deal record with line-item detail stored as a JSON custom field or Product association depending on plan tier.

ForceManager User records map to Freshsales User by email address. Owner assignments on Companies, Contacts, Opportunities, and Activities reference User IDs in ForceManager. We resolve these to Freshsales User records via email match. Users without a Freshsales match enter a reconciliation queue for admin provisioning before record import proceeds.

All z_ prefixed custom fields in ForceManager are extracted by querying the Fields endpoint to retrieve label-to-prefix mappings. We strip the z_ prefix and recreate fields as native Freshsales custom properties with human-readable names. Field types (text, number, date, picklist, checkbox) are mapped to Freshsales equivalent types. This process applies to all entity types (Account, Contact, Deal, Task). The z_ prefix itself is a ForceManager-specific convention and has no semantic value at the destination.

ForceManager Views (saved list filters) are extracted from the /views endpoint as configuration data rather than records. We document view structure including filter fields, operators, and sort order for manual recreation in Freshsales Views. Views cannot be exported as automation logic in either platform.