Migrate from Manta Business Management Software to Freshsales

Discovery and export verification

We audit the Manta BMS account to identify available record types (Contacts, Companies, Leads, Deals, Activities), estimate record counts, and verify what export mechanism the platform exposes. We request a sample export (CSV, Excel, or JSON if available) and validate field headers against the Freshsales field model. If the export is incomplete or unavailable, we discuss manual extraction options before proceeding. We also confirm the Freshsales account is provisioned and identify the target tier (Sprout, Blossom, Garden, Estate, or Forest) based on the customer's automation and workflow needs.

Mapping design and Freshsales schema setup

We design the field-level mapping from Manta export columns to Freshsales object fields. Standard fields map directly; non-matching fields are flagged for customer confirmation. We configure Freshsales schema including custom fields (based on the inventory of Manta custom fields for manual recreation), sales stages, lead status values, and any required picklist values. The Freshsales admin portal is used to configure these before any data import begins.

Owner and user reconciliation

We extract every distinct Owner referenced in the Manta export and match by email against the Freshsales User table. Any Manta Owner without a matching Freshsales User is placed in a reconciliation queue. The customer's Freshsales admin provisions missing Users (active or inactive based on whether the Manta user is still active). Migration cannot proceed past Activity import until all OwnerId references are resolved because OwnerId is required on Deals, Leads, and Activities in Freshsales.

Sandbox import and reconciliation

We run a test import into a Freshsales sandbox environment using production-like record counts. The customer reviews the imported records for field accuracy, relationship integrity (Contact-Account linkage, Deal-Contact linkage), and activity timeline completeness. We correct any mapping errors before production import. This step validates that the export format is stable and that Freshsales field types accept the mapped data without validation failures.

Production migration in dependency order

We run production migration in record-dependency order: Accounts (from Manta Companies), Contacts (with AccountId resolved), Leads, Deals (with OwnerId and Contact/Account lookups resolved), and Activities (Calls, Emails, Meetings, Tasks linked to parent records). Each phase emits a row-count reconciliation report before the next phase begins. We use the Freshsales REST API with batch processing and rate-limit handling to insert records efficiently.

Cutover and handoff

We freeze writes in Manta BMS during cutover, run a final delta migration of any records modified during the migration window, then set Freshsales as the system of record. We deliver a written inventory of any custom fields and attachments that could not be migrated for the customer to recreate manually. We do not rebuild Manta workflows or automations as Freshsales workflows inside migration scope; that is a separate engagement. We support a brief post-migration window for reconciliation issues raised by the customer's team.