Migrate from Manta Business Management Software to Salesforce Sales Cloud

Manta BMS Contact records with an associated lead status or qualification flag map to Salesforce Lead; Contacts tied to an established business relationship map to Salesforce Contact attached to an Account. We identify the split condition during scoping based on whatever status fields Manta BMS exposes in its export. Contacts without an email address are flagged as incomplete and held in a reconciliation queue. The original Manta BMS record ID is preserved in a custom field manta_id__c for audit and cross-reference.

Manta BMS Company records map directly to Salesforce Account. Company name becomes Account Name; industry and company size fields map to Industry and NumberOfEmployees on Account. We deduplicate Accounts by name during import using an external ID field to catch duplicates introduced by multiple Contacts from the same Company in the source export. Account is created before any Contact import so that the AccountId Lookup relationship is satisfied at Contact insert time.

Manta BMS Lead records map directly to Salesforce Lead. Lead source, status, and assigned owner fields migrate to the equivalent Salesforce Lead fields. If Manta BMS exposes a lead score or rating field, we map it to a custom field lead_score__c on Salesforce Lead. Owner resolution uses email matching against the Salesforce User table, with unresolved owners held in a reconciliation queue for the customer's admin to provision.

Manta BMS Deal records map to Salesforce Opportunity. Deal name becomes Opportunity Name; deal value maps to Amount; expected close date maps to CloseDate; and stage maps to StageName. The pipeline assignment from Manta BMS maps to a Salesforce Record Type and Sales Process that we configure before migration. If the Manta BMS export exposes closed-lost or closed-won reason fields, these map to Loss Reason and custom win reason fields on Opportunity.

Each unique stage name in the Manta BMS Deal export becomes a Salesforce StageName value within the designated Sales Process. We create the stage values before migration, mapping probabilities from whatever stage weighting Manta BMS exposes. Closed-Lost and Closed-Won stages are mapped to the Salesforce standard Closed Lost and Closed Won stage values. Stage ordering is preserved in the Sales Process configuration.

If Manta BMS exposes multiple deal pipelines or categories, each maps to a Salesforce Opportunity Record Type with its own Sales Process and Page Layout. This allows different lines of business to have scoped stage values and field visibility rules. The Record Type is set on Opportunity during migration using the pipeline mapping defined in scoping. If Manta BMS has only a single pipeline, we use the default Salesforce Opportunity Record Type without additional configuration.

Manta BMS User or Owner records referenced on Contact, Company, Lead, Deal, and Activity exports are resolved by email match against the Salesforce destination org's User table. We flag any Owner without a matching Salesforce User in a reconciliation report and hold record imports referencing that Owner until the customer provisions the User or remaps the Owner to an existing User. Active and inactive status is preserved to indicate whether the user account should be enabled in Salesforce.

Manta BMS call activity records map to Salesforce Task with TaskSubtype set to Call. Call duration, disposition, and any notes from the source export migrate to custom fields on the Task. The WhoId on Task points to the resolved Lead or Contact; the WhatId points to the related Opportunity or Account. ActivityDateTime is set to the original Manta BMS timestamp to preserve timeline ordering. We use the Salesforce Bulk API 2.0 for this phase to handle volume without hitting governor limits.

Manta BMS email engagement records map to Salesforce EmailMessage (the content body) linked to an Activity Task record (the timeline entry). The email subject and body text migrate as EmailMessage fields; HasAttachment flags whether the source record referenced a file. The WhoId links to the Lead or Contact; the WhatId links to the related Account or Opportunity. EmailMessage direction (inbound/outbound) is preserved in a custom field for reporting.

Manta BMS meeting records map to Salesforce Event. StartDateTime, EndDateTime, Subject, and Location fields migrate directly. Attendee information from the source export is stored as EventRelation records linked to the corresponding Lead, Contact, and User records. Event Subject is set to the Manta BMS meeting title. We resolve attendee WhoIds against the migrated Lead and Contact records using email as the matching key.

Manta BMS standalone task records map to Salesforce Task with Status, Priority, Subject, and ActivityDate preserved. Task assignment migrates by resolving the Manta BMS owner email to Salesforce OwnerId via the User mapping. Completed date and time migrate to CompletedDateTime on Task. If the Manta BMS export includes task description or notes, these migrate as the Task Description field.

Manta BMS note records map to Salesforce Note objects linked via ContentDocumentLink to the parent record. We set the parent as whichever object (Contact, Lead, Account, or Opportunity) the note was associated with in the source export, resolving by email and record ID where available. Note title and body text migrate directly. If Manta BMS exposes note creation timestamps or modified dates, these are preserved as Note CreatedDate for audit purposes.

Manta BMS custom fields on Contact, Company, Lead, and Deal records cannot be migrated. The platform does not expose custom field definitions or metadata through any documented API or export format. We identify and document every custom field present in the source export during scoping so the customer knows which data will not carry forward. The customer's admin creates matching custom fields in Salesforce and populates them manually or through a separate data entry project after migration.

Manta BMS file attachments linked to Contact, Company, Lead, or Deal records cannot be migrated. No public export endpoint or documented file storage access was found in Manta BMS. We flag any references to attachments in the source export so the customer knows which files are not carried forward. The customer's admin can re-upload key attachments post-migration if the files are available locally.