Migrate from Manta Business Management Software to HubSpot

Manta contacts map directly to HubSpot contacts. Email, phone, name, job title, and address fields translate field-for-field. Owner resolution runs by email match against HubSpot users. Unmatched owners are flagged and assigned to a fallback HubSpot owner before the migration commits.

Manta company records map to HubSpot company records. Company name, domain/website, industry, employee count, and annual revenue translate directly. Parent-company relationships in Manta map to the HubSpot parent company association field. Multi-company contacts collapse to the primary company with secondary companies stored as associations.

Manta deals map to HubSpot deals. Deal name, amount, close date, and owner translate field-for-field. Manta's deal stage names map to HubSpot pipeline stage names via a value-by-value mapping table. Each Manta deal pipeline becomes a separate HubSpot deal pipeline object.

Manta supports a single pipeline per workspace. If Manta has multiple deal pipelines defined, each becomes a separate HubSpot deal pipeline. Stage names are mapped value-by-value into HubSpot pipeline stages. Stage probabilities are assigned based on HubSpot's default stage model; your admin adjusts these post-migration.

Manta tasks and activities map to HubSpot engagement tasks. Task subject, body, due date, status, and owner translate directly. Completed status maps to HubSpot's task completion flag. Tasks linked to specific contacts or deals carry their association through to HubSpot.

Manta notes migrate as HubSpot engagement notes attached to the relevant contact, company, or deal record. The original note body, creation timestamp, and owner ID are preserved as metadata fields on the HubSpot engagement note. Associations to related CRM records are maintained so note context is retained after migration.

Manta user records resolve to HubSpot users by email address. Active Manta users with matching HubSpot email addresses receive their assigned records automatically. Inactive Manta users or users without a HubSpot account are flagged and reassigned to a fallback HubSpot owner before the migration runs.

Manta custom fields on contacts create HubSpot custom contact properties. All Manta field types (text, number, date, picklist, checkbox) map to the nearest HubSpot property type. Picklist values migrate as HubSpot option sets with the same labels. The HubSpot admin must create these properties in the portal before the migration runs.

Manta custom fields on deals create HubSpot custom deal properties. Date fields become HubSpot date properties. Number fields become HubSpot number properties with the same precision. Picklist fields become HubSpot deal property option sets. Your admin pre-creates these in HubSpot Settings > Properties before data lands.

Manta invoice line items map to HubSpot line items. Product name, quantity, unit price, and total map directly. Line items are associated with the corresponding HubSpot deal. Manta invoice status (paid/unpaid/overdue) maps to a HubSpot custom line item property for reporting continuity.

Manta business management objects that have no direct HubSpot equivalent (e.g., subscription records, project milestones) are preserved as HubSpot custom objects or as custom properties on the closest standard object. The mapping plan identifies these before the migration and your admin approves the placement.

Files attached to Manta contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files, then associated back to the relevant CRM record. File size limits apply — HubSpot caps individual files at 250MB. Files exceeding this threshold are flagged for manual download.