Migrate from ForceManager CRM to HubSpot

ForceManager accounts map directly to HubSpot companies. The account name, website domain, industry, employee count, and annual revenue fields transfer as HubSpot company properties. Multi-address accounts use HubSpot's single address field set per company. If an account has multiple locations, we concatenate the primary address fields and append secondary addresses as a custom property for reference.

ForceManager contacts map 1:1 to HubSpot contacts. All standard fields (first name, last name, email, phone, job title) transfer directly. The contact's associated account link resolves to the HubSpot company via domain or email-domain matching. We also preserve the original created date as a custom property and flag any duplicate email contacts for review to avoid merging errors.

ForceManager opportunities map to HubSpot deals with pipeline and stage name translation. The opportunity amount, close date, and probability transfer as HubSpot deal properties. Stage history in ForceManager is preserved as a custom text field in HubSpot for audit continuity.

ForceManager pipelines and their stage names require mapping to HubSpot deal pipelines and stages. We create a HubSpot pipeline for each ForceManager pipeline, map stage labels value-by-value, and set probability percentages per stage in HubSpot's pipeline configuration. Where a ForceManager stage lacks a direct HubSpot counterpart, we create a custom stage label and optionally capture the original stage entry timestamp as a custom date property for audit continuity.

ForceManager calls and emails migrate as HubSpot call and email engagement records on the associated contact timeline. Meetings migrate as HubSpot meeting events with original start/end times, subject, and body preserved. Owner attribution is resolved by email match. Call duration and outcome are stored as custom properties, while meeting location is mapped to the HubSpot meeting location field, ensuring complete activity history.

ForceManager tasks migrate to HubSpot tasks with subject, description, due date, and status. Completed task status maps to the HubSpot task completion flag. Open tasks retain their original due dates and assignee information. Priority levels are translated to HubSpot task priority values, and any recurring task patterns are noted as custom properties for manual re-creation in HubSpot.

ForceManager notes transfer as HubSpot engagement notes on the associated contact or company record. The note body text, creation date, and owning user all map to HubSpot's note properties with timestamps preserved. If notes contain file attachments, we upload them to HubSpot Files and link them to the note record; tags are imported as custom text properties, and any privacy flags are translated to HubSpot's note visibility settings.

ForceManager Sales Orders have no native HubSpot equivalent. On HubSpot Enterprise plans, we create a custom object named 'Order' with properties mirroring the ForceManager order fields. On lower tiers, order data attaches to the related Deal as custom properties or a notes attachment.

Sales order line items (product, quantity, unit price, discount) require a custom object on HubSpot Enterprise or map to a structured text property on the Order or Deal if a custom object is not available in the current HubSpot plan.

ForceManager owner IDs are internal integers with email addresses. We resolve each ForceManager owner to a HubSpot user by email match. Unmatched owners are flagged before migration; their records route to a designated fallback owner or remain in a pre-migration hold list.

All ForceManager fields prefixed with z_ are custom fields stored as text. We read each z_ field's actual data type from the ForceManager field configuration, then create the corresponding HubSpot custom property with the correct type (text, number, date, dropdown, checkbox) before importing values.

ForceManager events linked to accounts or contacts migrate as HubSpot meetings with original start time, end time, location, and subject. The event description and owning user are preserved. Events without an associated contact are linked to the primary company record.

Documents attached to ForceManager accounts, contacts, or opportunities are downloaded and re-uploaded to HubSpot's file storage, then linked to the corresponding HubSpot record. File size limits follow HubSpot's file upload constraints. During re‑upload we preserve the original file name, MIME type, and creation date as HubSpot file metadata, and link each file to its source record. If a file exceeds HubSpot's size limit, it is flagged for manual review.

ForceManager workflow definitions (stage-based routing, mandatory activity triggers, role-based qualification rules) are internal to ForceManager and have no export path. We export the workflow configuration as a structured JSON document for your HubSpot admin to reference when rebuilding in HubSpot Workflows.

ForceManager field metadata (required/optional flags, field labels, pick-list value sets) is read from the ForceManager Fields API. We use this to configure required flags and dropdown value sets on the corresponding HubSpot custom properties during migration setup. Default values are transferred, and validation rules like character limits are mapped to HubSpot property validation settings. Hidden fields are flagged for optional inclusion as custom properties if needed after go‑live.