Migrate from Cronberry to Odoo CRM

Cronberry Contacts map to Odoo res.partner records with address_type set to contact. Segment memberships and tag associations migrate as Odoo Mailing List subscriptions (mailing.contact) and ir.attachments with tag metadata. We run a deduplication pass before import: matching on email, name, and phone to flag probable duplicates from Cronberry's known repeat-contact reliability issues. The customer reviews the deduplication report before final insert.

Cronberry Companies map to Odoo res.partner with address_type set to company. Cronberry's company schema varies by implementation and may include custom fields; we extract the full field set during export scoping and map each to a corresponding res.partner field or custom field created in the destination Odoo database before import.

Cronberry Campaigns carry channel information (Email, SMS, Push, WhatsApp), timing rules, and target segment assignments. These map to Odoo crm.lead records with the campaign name stored in the Odoo campaign_id reference field. Cronberry's campaign-level audience logic is not directly migratable; we preserve campaign name, date range, and target segment names as fields on each crm.lead so the customer's admin can recreate segment targeting in Odoo's CRM filters and server actions.

Cronberry Smart Segments are built from field-value conditions with no exportable schema. We reverse-engineer segment membership by querying which contacts belong to each segment, then document the implied conditions (field + operator + value) in a format the customer's admin can enter into Odoo's mailing list filter builder. The segment names and member contact IDs migrate as Odoo Mailing List records and mailing.contact subscriptions. Segment logic itself requires manual rebuild in Odoo.

Cronberry tracks behavioral events (opens, clicks, push interactions) per contact. We map these to Odoo mail.message records linked to the res.partner parent. Each event type becomes a mail.message with subtype note, preserving the original Cronberry timestamp and event name in the message body. Cronberry's behavioral event schema may require field normalization since event properties differ from Odoo's standard activity model.

Cronberry User and Agent records map to Odoo res.users. We resolve users by email match. Any Cronberry User without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision the corresponding Odoo login before record import resumes. Role and permission structures differ significantly between platforms and are documented separately for the admin to reconfigure in Odoo's Access Control management.

Cronberry message templates with personalization variables are extracted and mapped to Odoo mail.template records. We preserve template subject, body content, and variable placeholders. Rich formatting may require adjustment since Cronberry and Odoo use different template markup languages. SMS and Push templates map to Odoo's sms.template and mail.mass_mailing models respectively if those apps are installed.

Cronberry Form definitions including field structure, conditional logic, and submission targets are extractable as a schema. We map the field structure to an Odoo Survey (survey.survey) if Odoo Survey app is installed, or to a custom model (ir.model and ir.model.fields) if the customer prefers a CRM-integrated form. Visual drag-and-drop layout cannot be preserved 1:1; we document the field order and conditional rules for manual recreation in Odoo Studio.

Cronberry's multi-channel setup stores channel credentials and configuration. We migrate channel associations to contacts as tags on res.partner records. Channel authentication credentials (API keys, sender IDs, WhatsApp Business Account IDs) cannot be exported and must be reconfigured in Odoo's corresponding app (Email Marketing, SMS, Push Notification) post-migration.

Cronberry's caller assignment and follow-up tracking logs map to Odoo mail.activity records on the related res.partner or crm.lead. Activity type, due date, summary, and assigned user migrate to the corresponding Odoo fields. Cronberry's follow-up statuses map to Odoo activity type categories (call, email, meeting, todo).

Cronberry custom fields on Contact, Company, and Campaign records are extractable from the database schema where available. We create corresponding custom fields on the Odoo res.partner and crm.lead models before migration using Odoo Studio or direct XML definition. Field type mapping follows: Cronberry text becomes Odoo char or text, numeric becomes float or integer, date becomes date, checkbox becomes boolean, dropdown becomes selection.

Cronberry Landing Pages are rendered assets with no standard API export path. We do not migrate Landing Pages as structured data or HTML content. We document the list of existing landing page URLs, form targets, and conversion goals so the customer's team can recreate them in Odoo using the Website builder (if Odoo Website app is installed) or a third-party landing page tool post-migration.