Migrate from Agentbox to Twenty CRM

Agentbox contacts map to Twenty People. Standard fields (first name, last name, email, phone, mobile, address) transfer directly. Buyer/tenant property criteria and contact categories are preserved as custom fields on the People record in Twenty. All data is validated against source exports before import to maintain accuracy.

Agentbox contact categories (tags used to segment buyers, tenants, vendors, etc.) have no native equivalent in Twenty People. FlitStack creates a 'Contact_Category__c' pick-list field and populates it with the source category values so filtering and segmentation logic is preserved. This ensures consistent reporting across both platforms.

Agentbox companies map to Twenty Companies. Fields including company name, trading name, ABN/ACN, industry, phone, website, and address transfer directly. Parent-company hierarchies in Agentbox are modeled via a 'Parent_Company__c' relation field in Twenty. This approach preserves organizational context and supports reporting by parent entity.

Agentbox deals map to Twenty Opportunities. Deal name, sale price, commission amount, stage, expected settlement date, and owner all transfer. Stage names map value-by-value to Twenty's Opportunity stage pick-list. Commission splits and linked property references are written to custom fields during the migration.

Agentbox property and listing records have no equivalent in Twenty's standard object set. FlitStack creates a 'Property__c' custom object with fields for address, listing status, asking price, inspection date, and listing agent — linked to the associated company and primary contact.

Agentbox agent profiles (staff records) map to Twenty Workspace Members. Owner resolution happens by email match — each Agentbox owner email is matched against Twenty user emails. Unmatched owners are flagged for pre-migration invitation or fallback assignment. This ensures every deal has a responsible user.

Agentbox buyer/tenant property criteria (budget range, property type, location preferences) attached to contacts migrate as structured custom fields on People: 'Requirement_Budget_Min__c', 'Requirement_Budget_Max__c', 'Requirement_Property_Type__c', 'Requirement_Location__c'. These fields are defined in Twenty's data model before import and populated during the people phase, preserving all preference details for reporting and follow‑up.

Notes and tasks logged against Agentbox contacts, companies, and deals transfer to Twenty Notes and Tasks. Original timestamps and owning agent are preserved. Notes attached to contacts land on the corresponding People record. This mapping maintains historical context for each entity throughout the migration.

Agentbox file attachments on records (photos, documents, contracts) are not included in CSV exports. FlitStack downloads these to a temporary, secure bucket and provides a file manifest so you can re-upload them to Twenty or your preferred storage after migration.

Agentbox deal commission splits across agents have no native equivalent in Twenty. FlitStack creates 'Commission_Split__c' text fields on Opportunities and records each agent's percentage so the financial split logic is preserved for reference. This enables accurate commission reporting and supports reconciliation after go‑live.

Agentbox portal access settings and contact‑facing login accounts do not transfer. Twenty's contact‑facing features (if used) require separate configuration post‑migration. We export the portal user list as a reference for rebuilding access. This exported list helps you re‑create user roles and permissions in Twenty's settings.