Migrate from Manta Business Management Software to Microsoft Dynamics 365 Sales

Export availability and format validation

We start by confirming what Manta BMS can actually export. Since there is no documented public API, we assess the platform's built-in export capability (CSV, Excel, or custom file) and validate the format's field coverage during a scoping call with the customer. We review a sample export file to identify column headers, record counts per object, and any structural gaps. If the platform requires manual intervention or a custom data request to produce a full export, we factor that delay into the timeline before proceeding.

Discovery and destination org review

We audit the Manta BMS export for record counts (Contacts, Companies, Leads, Deals, Activities), custom field presence, owner list, pipeline stage values, and any data quality issues. In parallel, we review the Microsoft Dynamics 365 Sales destination org (or set one up if it does not exist yet) to confirm the licensed edition (Sales Professional at $65/user or Sales Enterprise at $105/user), identify existing users, and note any validation rules or required fields that could block import. We deliver a written migration scope document covering object coverage, unmappable data, and owner reconciliation requirements.

Owner reconciliation and user provisioning

We extract every distinct owner email from the Manta BMS export and match against the Microsoft Dynamics 365 Sales destination org's User table. Owners without a matching Dynamics User are listed in a reconciliation report for the customer's admin to provision. This step must complete before any record import begins because OwnerId is a required reference on Leads, Deals, and Activities in Dynamics 365. We set a hard checkpoint here: migration does not proceed past this step until the owner list is confirmed clean.

Data profiling and cleansing

We run a data profiling pass on the Manta BMS export to identify duplicate contacts (same email, different record), incomplete required fields, inconsistent date formats, and malformed text entries. We flag duplicates and propose a de-duplication strategy (typically keeping the most recently modified record or the record with the most complete fields). We normalize address formatting and standardize date fields to the ISO 8601 format that Dynamics 365 expects. Cleansing output is reviewed with the customer before production migration begins.

Pipeline stage and status mapping configuration

We configure Microsoft Dynamics 365 Sales with the Manta BMS pipeline stage values mapped to Sales Process and StageName values in the destination org. If Manta uses stage names that do not match Dynamics 365 defaults (Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost), we add them to the appropriate Sales Process picklist before import so no Opportunity record is rejected by a validation rule. The same is done for LeadStatus picklist values if Manta uses non-standard lead lifecycle stages.

Production migration in dependency order

We run the production migration in the correct record-dependency sequence: Dynamics 365 Users (validated from step 3), Accounts (from Manta Companies), Contacts (with AccountId resolved), Leads, Opportunities (with AccountId, OwnerId, and Sales Process resolved), and Activity records (Tasks and Events via the Dataverse API with batch chunking). Each phase emits a row-count reconciliation report comparing migrated records to the Manta export counts. Custom fields and attachments are not migrated; they are documented as excluded from scope in the final handoff report.

Cutover, validation, and admin handoff

We freeze Manta BMS writes during cutover, perform a final delta migration of any records modified during the window, and enable Microsoft Dynamics 365 Sales as the system of record. We deliver a migration summary report with record counts per object, excluded items (custom fields, attachments), owner reconciliation status, and the pipeline stage mapping reference. We do not rebuild Manta BMS automations or workflows in Microsoft Dynamics 365 Sales ; we deliver a written inventory of any automations identified in the source export for the customer's admin to rebuild using Microsoft Dynamics 365 Sales Flow or Power Automate.