Migrate from ForceManager CRM to Salesforce Sales Cloud

ForceManager Companies map to Salesforce Account. The company name, type, rating, phone, address, and responsible user fields map directly. The z_ prefix custom fields on Company records are introspected during schema extraction, recreated as Salesforce custom fields on Account, and populated during import. OwnerId is resolved by matching the ForceManager responsible user email against the Salesforce User table.

ForceManager Contacts map to Salesforce Contact. Each Contact has a required AccountId reference, so Accounts are imported first. The z_ prefix custom properties on Contact records (z_internal_currency, z_text_special, etc.) are resolved via the Fields endpoint and recreated as typed Salesforce custom fields on Contact. Contact Role assignments migrate to Salesforce Contact Role records on the parent Account.

ForceManager Opportunities map to Salesforce Opportunity. The Opportunity stage maps to StageName; responsible user maps to OwnerId. Closed-Lost and Closed-Won dates migrate as CloseDate and StageName values. ForceManager does not have a native equivalent of Salesforce's AccountId required field on Opportunity, so we resolve the parent Company reference during the transform phase and set AccountId before Opportunity insert.

ForceManager Activities are a single object covering calls, meetings, and field visit logs. We split by activity type: call activities map to Task with TaskSubtype=Call and CallDisposition; meeting activities map to Event with StartDateTime and EndDateTime; field visit activities map to Task with a custom field capturing GPS coordinates. Activity linked Contact and Company references resolve to Salesforce WhoId and WhatId at migration time.

ForceManager Events export includes event name, date/time, location, and GPS coordinates. We map StartDateTime and EndDateTime directly, store the GPS latitude and longitude as custom fields on the Salesforce Event (z_latitude__c, z_longitude__c, renamed to human-readable equivalents at the destination), and link attendees via EventRelation records pointing to the resolved Contact or User.

ForceManager Tasks map to Salesforce Task with Status, Priority, ActivityDate, and Subject preserved. Assignee resolves via Owner mapping by email. Completed tasks retain their Status=Completed value; open tasks are set to Not Started. Tasks linked to Companies or Contacts resolve WhatId and WhoId respectively before insert.

ForceManager Sales Order and Sales Order Line entities do not have a native Salesforce Sales Cloud equivalent without CPQ. We map Sales Orders to Opportunity Products if the destination includes a price book, or we create a custom Order object (Order__c) with Order Line items (Order_Line__c) in Salesforce if the customer needs a standalone order record. The mapping decision is made during scoping based on the customer's quoting workflow.

ForceManager Users are extracted via the /users endpoint. Every record in ForceManager carrying an owner assignment (Companies, Contacts, Opportunities, Activities, Tasks) references a User ID. We match by email against the Salesforce User table. Any ForceManager User without a matching Salesforce User enters a reconciliation queue for the admin to provision before migration resumes.

Every custom field in ForceManager carries a z_ prefix in the API payload. The display label, field type, and picklist values must be retrieved from the Fields endpoint or schema documentation. We introspect during extraction, then pre-create Salesforce custom fields with human-readable API names (removing the z_ prefix) and matching data types before any data import begins. This ensures the migration transform can map values directly to typed fields rather than working around system-prefixed keys.

ForceManager Views are saved list filters exported via /views. These are configuration rather than data. We document view structure, filter criteria, and sort order in a written handoff for the customer's admin to recreate as Salesforce List Views. Views referencing custom z_ fields include the field label mapping so the admin can recreate the filter against the renamed Salesforce field.

ForceManager List membership is derived from saved view filters or static membership. We reconstruct membership by applying the same filter logic at the destination or by creating static lists from the membership snapshot at migration time. If the customer uses Salesforce, we create Campaign members for static lists; if they use a separate segmentation tool, we deliver a CSV of list membership for import.

ForceManager file attachments on Companies, Contacts, and Opportunities are not accessible via the REST API. We flag all attachment dependencies during scoping and advise customers to download attachments from the ForceManager web UI before the migration window. We provide a written attachment inventory (record ID, attachment name, file type, linked entity) so the customer's admin can upload via Salesforce Files or ContentDocumentLink post-migration. We cannot automate attachment extraction and cannot guarantee completeness without customer-provided files.