Migrate from Altcraft to Twenty CRM

Altcraft's unified Profile record maps to Twenty CRM's Person object. Every Profile field (email, phone, name, custom properties, behavioral attributes) maps to the corresponding Person field or a custom field on Person. We preserve the original Altcraft Profile ID in a custom field altcraft_profile_id__c for audit and reconciliation. The Profile's channel subscription status (email, SMS, push) migrates to a multi-select picklist field channel_subscriptions__c on Person.

Altcraft stores behavioral events (page views, email opens, link clicks, purchases, custom events) as time-stamped records linked to the Profile. These map to a custom object BehaviorEvent (with EventType, EventDate, EventProperties, and PersonId lookup) in Twenty CRM, preserving the full timeline against the Person record. If the customer does not require historical behavioral data, we can omit this phase and reduce migration scope.

Altcraft's Company object (if present) maps directly to Twenty CRM's Company object. Company name, domain, industry, size, and address fields map 1:1. Custom Company fields migrate as typed custom fields on the Twenty Company object.

Static segments in Altcraft are straightforward lists of Profile IDs. We export the segment membership as a Person-level custom field segment_membership__c (multi-select) or as a custom Tag object linked to Person. The customer chooses the representation during scoping. This approach preserves segment membership without requiring Twenty to support dynamic segment logic.

Dynamic segments in Altcraft use real-time behavioral criteria (last activity within 30 days, channel equals email, event count > 5) that have no native equivalent in Twenty CRM's current release. We export the segment definition as a structured written rule set. The customer rebuilds these as Twenty Views (which are manual filters) or documents them for use with an external segmentation tool. We do not migrate dynamic segment logic as executable code.

Altcraft Campaign records (send history, open rates, click rates, channel assignment) map to Twenty CRM Opportunity records if the customer wants campaign performance tracked in the CRM. Campaign metrics migrate as custom fields on Opportunity (send_count__c, open_count__c, click_count__c, channel__c). If the customer does not track campaign performance in the CRM, we export a Campaign Performance Report as a structured CSV and skip the Opportunity mapping.

Altcraft message templates (email subject, body, A/B variants) export in standard formats. Twenty CRM does not have a native template library, so we deliver templates as a structured CSV with template_name, subject, body, and variant fields. The customer's team copies templates into their chosen email sending tool (Gmail integration, external ESP) or recreates them in Twenty's available tools.

Altcraft's channel configurations (sender IDs, API credentials for SMS, approved email sending addresses, messenger tokens) are platform-specific credentials that do not migrate. We export a Channel Inventory document listing every active channel, its credentials, and the recommended replacement integration in Twenty (Twilio for SMS, SendGrid for email, Slack for messaging). The customer's admin reconfigures these in the destination platform.

Altcraft Products map to a custom object Product in Twenty CRM. We create the Product custom object with fields for name, sku, price, description, and category. If the customer uses Products for e-commerce tracking, we also create an Order custom object linked to Person and Product.

Altcraft Orders (linked to Profiles and Products) map to a custom Order object in Twenty CRM with fields for order_id, order_date, total_amount, status, person_id, and product_id lookups. We resolve the Person and Product references at migration time so that the relationships are established in the destination.

Altcraft Form definitions (field structure, question types, submission logic) export as structured JSON. We deliver a Form Inventory document listing every form, its fields, and the submission mapping. Twenty CRM does not have a native form builder, so the customer uses the form inventory to rebuild forms in a third-party tool (Typeform, HubSpot Forms, or custom) or to set up web-to-person integrations.

Altcraft Control Groups are holdout groups assigned to specific Profile IDs for campaign comparison analytics. We preserve Control Group membership as a custom field on Person (control_group__c, text). The destination platform must support Control Group logic natively or the customer uses this field for manual segmentation. We flag this limitation in the migration scope.