Migrate from Maple CRM to Twenty CRM

Maple CRM Client records map to Twenty People objects. Client contact details, address, nationality, passport data, and linked Cases migrate as standard fields plus custom fields. We identify all immigration-specific custom properties on the Client record during discovery and recreate them in Twenty's Settings → Data Model before import. Clients are the parent entity for Cases, so all Client records must be migrated before the Case import batch runs to satisfy foreign-key references.

Maple CRM Lead records (source, status, assigned executive, follow-up dates, intake data) map to Twenty People objects with a separate tag or custom field to distinguish them from converted Client records. We preserve the lead source and assigned executive fields as custom properties on the People record in Twenty.

Maple CRM Cases map to Twenty Opportunities by default. Each Case links to a Client (mapped to the People record already imported). Case process stages (Application, Review, Submission, Approval, Denial, Appeal) migrate as Opportunity stage values that we configure in Twenty's pipeline settings before import. Stage history timestamps preserve as a custom activity-logging field on the Opportunity record. Cases with child sub-cases require a custom object in Twenty if the relationship needs to be tracked explicitly.

Documents attached to Cases or Clients in Maple CRM (passport scans, proof of funds, visa applications) migrate as binary blobs with metadata (document type, upload date, related record reference). We store document type as a custom field on the Activity record and preserve the upload timestamp. Large binary files (scans over 25 MB) may require chunked transfer or external storage link in Twenty.

Maple CRM Quotations (line items, pricing, status) migrate as Twenty Opportunity records with line item entries. We create Opportunity records with the quotation total, status, and creation date; line items become sub-records on the Opportunity. PDF output from the Quotation Builder does not migrate; only the underlying data record transfers.

Maple CRM Invoices migrate as a custom Invoice object in Twenty with fields for invoice number, line items, amounts, payment terms, outstanding balance, and payment history. We create the custom object and all required fields in Twenty's Settings → Data Model before the import batch runs. Payment status and instalment schedule data preserve as custom fields on each Invoice record.

Generated Agreement records from Maple CRM's Agreement Generator migrate as Opportunity or custom Contract records with linked Client reference. The agreement template definitions with macro placeholders are not API-exportable from Maple CRM; we document the template structure so the customer can rebuild it in Twenty. Renewal dates migrate as custom date fields on the Contract record.

Support Request records from Maple CRM's Support Request Management module migrate as Task records or a custom Support Request object in Twenty. We migrate status, priority, assignee, and timestamps. TAT (Turnaround Time) tracking and SLA escalation rules do not migrate; we document the queue structure and escalation thresholds for the customer's admin to rebuild in Twenty as workflow rules.

Maple CRM user accounts with role-based access control map to Twenty Members. We export user records with role and team assignments and match by email during the Twenty Member provisioning step. Any Maple CRM user referenced as an Owner on Cases or Deals must have a matching Twenty Member record created before those object imports run.

Maple CRM automation rules (stage-change triggers, email notifications, follow-up reminders) are platform configuration with no API export path. We do not migrate automation definitions. During scoping, we inventory every active automation the customer has configured and deliver a written map of triggers, conditions, and actions with recommended Twenty Workflow equivalents. The customer or their Twenty implementation partner rebuilds each automation post-migration.