Migrate from Altcraft to Odoo CRM

Altcraft Profiles are unified records combining contact identity, behavioral event history, channel subscriptions, device metadata, and all custom fields into a single object. We split this into Odoo Partner records: personal identity data (name, email, phone, address) becomes Contact (and its parent Company/Partner record). Behavioral event history, channel subscriptions, and device context migrate as custom fields on the Contact and as a structured JSON blob in a dedicated ir.attachment linked to the Contact for audit trail. Custom Profile fields map to Odoo custom fields on res.partner with appropriate type conversion (string, date, integer, selection). We preserve the original Altcraft Profile ID as an external_id field for reconciliation.

Altcraft's embedded company data within Profiles maps to Odoo res.partner records of type company. The company name, domain, industry, employee count, and revenue range from Altcraft's company fields become their Odoo equivalents. If a single Contact belongs to multiple companies in Altcraft, we create a primary Company Partner and link secondary affiliations as Contact tags or as dedicated Partner relationships.

Static segments in Altcraft are straightforward list transfers to Odoo res.partner groups. Dynamic segments based on real-time behavioral criteria require reimplementation in Odoo: we export the full segment definition (filter criteria, time windows, SQL joins, behavioral thresholds) as a structured description document and recommend the Odoo Automated Action equivalent using domain filters on res.partner. Static segments that reference Profile lists migrate as Odoo Groups with members assigned directly. The customer admin rebuilds dynamic segment logic post-migration using Odoo's domain filter builder.

Altcraft Campaign records (send history, open and click analytics, channel assignment) migrate to Odoo CRM Campaign with campaign name, description, start and end dates, and target partner sets. Performance metrics (opens, clicks, unsubscribes) transfer as structured fields. Channel assignment (Email, SMS, Push) maps to Odoo's mailing.channel configuration. Campaign Master and A/B test results from Altcraft Cloud Pro tier are preserved as campaign-level custom fields in Odoo.

Altcraft Scenarios are visual workflow builders with conditional branches, loop constructs, time delays, and API webhook calls that have no portable export format. We do not migrate Scenarios as executable code. We export a structured Scenario inventory document listing every Scenario's name, trigger event, condition tree, action sequence, and referenced Profile and Segment IDs, with a written recommendation for Odoo Automated Action equivalents using ir.actions.server and ir.cron configurations. The customer's Odoo admin or implementation partner rebuilds the logic in Odoo's Actions menu post-migration.

Altcraft message templates export in standard formats (HTML, plain text) with merge field placeholders. A/B test variants are preserved as separate template records. We map Altcraft merge fields to Odoo's Jinja2-style {{object.field}} syntax in mail.template records, and convert channel-specific templates (SMS, Push) to Odoo Mass Mailing templates scoped to the appropriate mailing.channel. Template assets (images, logos) transfer as Odoo ir.attachment records linked to the template.

Altcraft product catalog records map to Odoo product.template with name, default_code (SKU), list_price, standard_price, and product type (service vs consumable vs stockable). Product images migrate as ir.attachment records linked to the product.template. Variant attributes from Altcraft (size, color) map to Odoo attribute lines on the template. If Altcraft products include e-commerce pricing rules tied to customer segments, those rules are documented for rebuild in Odoo pricelists.

Altcraft order history linked to Profiles migrates to Odoo sale.order records with order reference, date, partner (from Profile), order lines (from Altcraft order items), and sale status. Order total and tax calculations transfer from Altcraft. If the destination Odoo instance includes the Inventory or Accounting modules, we link the sale.order to the appropriate picking and invoice records during migration. Historical orders are set to sale.done state to prevent accidental workflow triggers.

Altcraft Control Groups are campaign holdout groups assigned to specific Profile IDs for comparative analytics. We preserve Control Group membership as a res.partner.category tag (e.g., 'Control Group: Q1 Email Test') and set the corresponding CRM Campaign Member status to 'Excluded' for those Contacts. We preserve the original Control Group assignment in a custom field on the partner record so comparative analytics can be re-established post-migration in Odoo's reporting tools.

Altcraft loyalty tiers, points balances, and promo code pools tied to Profiles migrate to Odoo loyalty.program records and associated loyalty.card records per partner. Tier thresholds map to Odoo's loyalty level definitions. Promo code rules map to Odoo coupon and promotion rules. If the destination Odoo instance does not include the Loyalty app, we deliver loyalty data as structured CSV with clear column headers for the customer's admin to configure the Loyalty program post-migration.

Altcraft user-defined fields on the Profile object export as structured columns in the profile CSV. We create matching custom fields on Odoo res.partner using ir.model.fields with the appropriate ttype (char, text, date, datetime, integer, float, selection, many2one). Relational fields (many2one to other objects) require pre-creation of the destination object schema before field migration. We flag any Altcraft field types that cannot be directly represented in Odoo (e.g., JSON blobs) and recommend storing these as ir.attachment binary records with a descriptive filename.

Altcraft Form definitions and NPS survey question structures export cleanly from the UI. We migrate form schema (question types, required flags, branching logic) to Odoo survey records using the survey module. Responses already embedded in Profile records migrate as standard Profile data to Contact custom fields. Standalone response logs transfer as survey.user_input records linked to the responding partner. Survey URLs and embed codes do not migrate and must be recreated in Odoo.

Altcraft channel configurations (Email sender IDs, SMS provider credentials, approved sender addresses, Web Push credentials, Messenger tokens) must be re-established in Odoo's Mailing Channel settings. We export the channel names, types, and metadata from Altcraft and deliver a configuration guide mapping each channel to its Odoo mailing.channel equivalent. API credentials do not transfer for security reasons and must be re-entered by the customer's admin in Odoo Settings.

Altcraft email engagement records (send timestamp, open timestamp, click timestamp, unsubscribe action) migrate to Odoo mail.message records linked to the parent res.partner record. Email body content is stored as mail.message body HTML. Engagement metrics (opens, clicks) migrate as custom fields on mail.message for reporting. Thread-level email conversations in Altcraft map to Odoo's mail.thread model with message_ids preserved for conversation continuity.

Altcraft call engagement records (call duration, disposition, recording URL) migrate to Odoo CRM Lead log records or to crm.phonecall model if the CRM phonecalls module is installed. We preserve call duration, timestamp, and disposition as structured fields on the log entry. Recording URLs are stored as ir.attachment records linked to the partner. Call assignments migrate by resolving Altcraft owner ID to the Odoo user responsible for the contact.