Migrate from CallPro CRM to Twenty CRM

CallPro Contact records map directly to Twenty Person records. Standard fields (name, phone, email, company association) map to Twenty's name, emails, and phone fields. Custom contact fields extract during the audit phase and pre-create as custom fields in Twenty before migration. Email history links attached to CallPro contacts migrate as activity records tied to the Person. Multi-database CallPro configurations require a workspace or team segmentation strategy in Twenty before contact import.

CallPro Company records map to Twenty Company records. The company name becomes the Company name field; domain and website become the domainName field. We match CallPro companies to parent Person records via the contact-company link or company name matching. Multi-database CallPro configurations may use Twenty workspace segmentation to preserve the original team or campaign separation.

CallPro Lead records map to Twenty Person records, preserving lead status, source attribution, and campaign association. Dialer log entries attached to CallPro leads migrate as Activity records linked to the Person. Lead scoring or qualification data stored as custom fields pre-creates in Twenty before migration. The customer reviews the intended Lead-to-Person pipeline after migration; CallPro does not have a separate unconverted-Lead concept that requires a different destination object.

CallPro Campaigns are a top-level object linking contacts, leads, and activities. We migrate campaign metadata (name, type, status, start and end dates) and campaign member associations (which contacts and leads were in which campaign). The campaign questionnaire logic and routing rules do not port; we flag this during scoping and document the questionnaire structure so the customer can rebuild as a Twenty workspace process or custom object logic.

CallPro campaign membership (which contacts and leads were enrolled in which campaign) maps to a Campaign field on the Person record in Twenty. For teams with complex multi-campaign enrollment histories, we evaluate whether to store campaign membership as a custom multi-select field on Person or as a dedicated Campaign workspace with Person membership records.

CallPro activity logs include call duration, disposition, notes, and timestamp. We map these to Twenty Activity records. Disposition codes require value mapping as terminology differs between platforms; we capture the CallPro disposition taxonomy during scoping and create a corresponding picklist or custom field in Twenty before migration. Activity timestamps preserve the original CallPro creation date.

CallPro Sales Orders and Quotes map to Twenty Opportunity records. Order headers, line items, pricing, quantities, and product references migrate directly. Order status and approval flags map to Opportunity stage and custom status fields. CallPro quotes migrate as Opportunity records with a quote flag; the customer configures a formal quoting workflow in Twenty post-migration.

CallPro custom fields on contacts, companies, and leads extract during the audit phase. We pre-create the equivalent custom properties in Twenty before any data import begins, matching field type to the closest Twenty type (text, number, date, picklist, multi-select). Field dependencies and conditional visibility rules do not migrate and must be rebuilt in Twenty.

CallPro tagging taxonomy exports and applies to matching Person and Company records in Twenty. Where the customer plans to use tags for segmentation and filtering, we store them as a custom multi-select field on Person. Alternatively, if Twenty Topic usage fits the workflow, we create TopicAssignment records. The customer chooses the tag strategy during scoping.

CallPro User records and owner assignment (owner on contacts, leads, companies) map to Twenty User records by email address match. Inactive users from CallPro preserve as historical assignments on migrated records. Active users must exist in Twenty before record import so that the owner field is satisfied at insert time.

File attachments linked to CallPro contacts, leads, or companies export and re-link in Twenty. We preserve filename and association mapping during migration. Large-volume attachment exports may require staged batch processing to avoid timeout. Customers on Twenty's hosted tier should verify attachment storage limits.

CallPro email template bodies and subject lines export as raw text. Merge field syntax differs between platforms (CallPro uses its own placeholder format versus Twenty's handlebars or similar). We provide a merge field mapping guide during the handoff. The customer reviews and updates templates post-migration; we do not handle merge field translation as part of migration scope.