Migrate from Manta Business Management Software to Twenty CRM

Manta BMS Contacts map to Twenty CRM Person records. Standard fields (name, email, phone, address) transfer directly. We flag any Manta custom contact properties during scoping because Twenty requires these fields to be pre-created in Settings before CSV import. Company affiliation from Manta maps to the Person's Company link in Twenty via a lookup that we resolve after Companies are imported first.

Manta BMS Company records map directly to Twenty CRM Company records. Company name, domain, industry, employee count, and address fields transfer where present. If the Manta export does not include company-contact linkage, we rebuild the Person-to-Company relationship during migration by matching on domain or company name as a secondary pass after both objects are imported.

Manta BMS Lead records with a distinct lifecycle status (new, contacted, qualified) map to Twenty CRM Person records tagged with a Lead type or source field. We preserve the original Manta lead status value in a custom field so the customer's admin can segment migrated leads in Twenty after import. Leads without a Manta counterpart in Contacts are imported as Persons with a source attribution to Manta.

Manta BMS Deals map to Twenty CRM Opportunity records. Deal name, value, stage, and expected close date transfer directly. Pipeline stage names from Manta must be reviewed and matched to Twenty stage options during scoping; stage probability percentages are not automatically carried and require manual configuration in Twenty's pipeline settings before migration.

Manta BMS activity records (calls, emails, meetings, tasks) map to Twenty CRM Tasks and Notes. We extract the activity type, timestamp, subject, body, and associated contact reference from the Manta export where linkage data is available. Activities without a clear associated record in the Manta export import as standalone Notes in Twenty, flagged as orphaned. Activity records with rich HTML content are converted to plain-text Notes.

Manta BMS Users referenced as Deal owners, Lead assignees, or Activity creators map to Twenty CRM Members. We match by email address. Any Manta user without an email match in the export goes to a reconciliation queue for the customer's admin to provision the corresponding Twenty member before record import resumes. Archived or inactive Manta users are excluded from migration unless explicitly requested.

Manta BMS custom fields on Contact records require pre-creation in Twenty CRM Settings before import. We inventory every custom field during scoping, verify its presence in the export, and pre-create the corresponding Twenty field with the correct data type (text, number, date, select) in the customer's Twenty workspace before the import phase begins. If a Manta custom field has no schema documentation, we flag it and exclude it from migration.

Manta BMS custom fields on Deal records map to Twenty CRM custom fields on the Opportunity object. We apply the same pre-creation workflow: inventory, verify export availability, create the field in Twenty, then import. Deal-level custom fields that reference picklist values require those options to be whitelisted in Twenty's field settings before import.

If Manta BMS contains custom objects beyond the standard Contact, Company, Lead, Deal, and Activity set, we map them to Twenty CRM Custom Objects. Twenty's data model supports custom objects with lookup relationships to standard objects (Person, Company, Opportunity). We pre-create the custom object schema in Twenty including all custom fields and relationship fields before any data loads. Custom object naming follows Twenty's conventions and is verified with the customer during scoping.

Manta BMS does not expose a documented file storage export, and Twenty CRM handles attachments as file uploads within its own interface rather than as importable records. We do not migrate attachments as binary files. If the Manta export includes file URLs or references, we note them in the migration inventory and the customer handles file re-upload manually post-migration.

Manta BMS tags and labels on Contact or Deal records map to a custom text field in Twenty CRM. We recommend a comma-separated custom field for simplicity, or a multi-select field if Twenty's field type supports it at the time of migration. Tag strategy is confirmed during scoping based on the customer's segmentation needs in Twenty.

Manta BMS Lead status values (new, contacted, qualified, unqualified) migrate as a custom select field on the Twenty CRM Person record. We extract the status from the Manta export and map each distinct value to a corresponding Twenty select option. The customer configures which status values represent active pipeline leads versus closed leads during scoping.

Manta BMS pipeline stage names (appointment scheduled, proposal sent, negotiation, closed won, closed lost) map to a custom select field on the Twenty CRM Opportunity record. We inventory every distinct stage value from the Manta export and pre-create matching select options in Twenty before Deal import. Probability percentages are noted in the mapping document for the customer to configure manually in Twenty's pipeline settings post-migration.

Manta BMS phone numbers on Contact and Company records map to Twenty CRM phone fields on Person and Company. We normalize phone number formats to a standard string representation during the transform phase. Multiple phone numbers (mobile, work, home) from Manta map to a single phone field in Twenty unless the customer's migration scope includes a multi-phone custom field setup.