Act! to Odoo CRM migration
We migrate Contacts, Companies, Opportunities, and Activity history from Act! into Odoo CRM — using Odoo's XML-RPC API to write into res.partner and crm.lead, configuring pipeline stages, and re-creating Act! Custom Tables as Odoo Studio modules.
FlitStack AI migrates res.partners, crm.leads, sale.order.lines, mail.activities and mail.messages from Act! to Odoo CRM, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

What moves from Act! to Odoo CRM?
Odoo CRM is an unusual destination from Act! because of Odoo's unified-partner model: Contacts and Companies share a single res.partner table differentiated by the company_type flag.
Read the full summary
Act!'s separate Contact + Company tables collapse into a parent-child res.partner structure where Companies are partners with company_type='company' and Contacts are linked partners with parent_id pointing at the company. Opportunities → crm.lead with type='opportunity'. The interesting work is the partner model conversion (which we automate during transformation) and the Studio module deployment for Act! Custom Tables. Odoo's open-source nature also means customers running Odoo Community edition (free) can't use Studio for custom modules; in that case we install custom modules via the Odoo manifest format, which requires a deployment window. Activity and History migrate to mail.activity (open) and mail.message (closed).
Company → res.partner (company_type=company)
Act! Companies map to res.partner with company_type='company' and is_company=True.
How it maps
These partners hold address, website, industry, and account-level fields.
Contact → res.partner (company_type=person, parent_id=Company partner)
Act! Contacts map to res.partner with company_type='person' and parent_id pointing to the Company partner.
How it maps
The unified partner table is Odoo's structural quirk; we resolve it during transformation.
Opportunity → crm.lead (type=opportunity)
Act! Opportunities map to crm.lead with type='opportunity' (qualified).
How it maps
Stage_id resolves to crm.stage record. partner_id links to the Contact partner; partner_name preserves the original Act! Company name.
Opportunity Product → sale.order.line (in linked sale.order)
Odoo separates pipeline (crm.lead) from quotes/orders (sale.order).
How it maps
We create a draft sale.order linked to the Opportunity's crm.lead and attach Opportunity Products as sale.order.line records. Products pre-created as product.template.
Activity (scheduled) → mail.activity
Act! scheduled Activities map to mail.activity records on the parent res.partner or crm.lead.
How it maps
Activity type (Call/Meeting/To-do) maps to mail.activity.type. Date_deadline preserves the scheduled date.
History (completed) → mail.message
Completed Act! History items map to mail.message records on the parent res.partner or crm.lead with message_type='comment' and the original timestamp preserved via the date field.
- Companyres.partner1:1
- Contactres.partner1:1
- Opportunitycrm.lead1:1
- Opportunity Productsale.order.linetransformed
- Activitymail.activity1:1
- Historymail.messagetransformed
+ 5 more in the mapping below
How Act! and Odoo CRM differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Act! | Odoo CRM |
|---|---|---|
| Contact + Company model | Separate Contact and Company tables | Unified res.partner with company_type flag and parent_id |
| Opportunity vs Lead | Single Opportunity object | crm.lead with type field (lead vs opportunity) |
| Custom objects | Custom Tables in Premium v18+ | Studio modules (Enterprise) or custom Odoo modules (Community) |
| Pricing | ~$30/user/mo Cloud or ~$370/user perpetual | Community free; Enterprise $31.10/user/mo (with app discount tiers) |
| Deployment | Cloud or on-premise | Cloud (Odoo.sh, Online) or self-hosted (Community/Enterprise) |
| Architecture | Standalone CRM | Modular suite (CRM is one of 80+ apps in the same DB) |
Act! to Odoo CRM field mapping
The 14 most-used fields of 14 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
ContactContactnameres.partner -
E-mailContactemailres.partner -
Phone (Business)Contactphoneres.partner -
Mobile PhoneContactmobileres.partner -
TitleContactfunctionres.partner
| Act! field | Odoo CRM field | Mapping | Note |
|---|---|---|---|
Contact.Contact | res.partner.name | direct | Odoo stores full name in a single field; pass through. |
Contact.E-mail | res.partner.email | direct | Lowercase. Odoo dedupe is configurable; default doesn't enforce email uniqueness. |
Contact.Phone (Business) | res.partner.phone | direct | Normalize to E.164 if available. |
Contact.Mobile Phone | res.partner.mobile | direct | Separate Odoo field. |
Contact.Title | res.partner.function | direct | Odoo job title field. |
Contact.Address fields | res.partner.street / street2 / city / state_id / zip / country_id | direct | state_id and country_id resolve to res.country.state and res.country records by name lookup. |
Company.Company | res.partner (company_type=company).name | direct | Required. is_company=True. |
Company.Web Site | res.partner.website | direct | Normalize URL. |
Opportunity.Name | crm.lead.name | direct | Pass through. |
Opportunity.Total | crm.lead.expected_revenue | direct | Numeric; currency from res.currency. |
Opportunity.Stage | crm.lead.stage_id | mapping | Translation table to crm.stage records. Probability auto-populates from stage default. |
Opportunity.Estimated Close Date | crm.lead.date_deadline | direct | ISO date. |
Activity.Subject / Date / Duration / Type | mail.activity.summary / date_deadline / activity_type_id | direct | Type-specific via mail.activity.type lookup. |
Note.Note Text | mail.message.body | direct | HTML body. RTF converted; embedded images extract to ir.attachment. |
What to watch for in a Act! to Odoo CRM migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Contact + Company collapse to single res.partner table
Odoo's unified-partner model means Act!'s separate Contact and Company records both become res.partner rows differentiated by the is_company flag.
How we handle it
Parent-child relationship (Contact.parent_id → Company) must be set explicitly during load. We handle the conversion in transformation but customers familiar with separate tables sometimes find Odoo's model counterintuitive at first.
Custom module deployment differs between Enterprise and Community
Act! Custom Tables become Odoo Studio modules (Enterprise) or hand-written custom Python modules (Community).
How we handle it
Community installations require a custom module zip with __manifest__.py deployed via the Odoo addons path and a server restart. We capture the Custom Table schema during scoping and deliver the appropriate artifact for the customer's Odoo edition.
Opportunity Products require sale.order creation
Odoo separates pipeline (crm.lead) from quotes (sale.order).
How we handle it
Act! Opportunity Products don't have a direct equivalent on crm.lead — we create a draft sale.order linked to the Opportunity and attach Products as sale.order.line records. Customers who don't want the Sales app installed get a JSON-serialized product list as a note instead.
Activity preserved-date requires XML-RPC create_uid override
Odoo by default stamps the API user as create_uid and the import time as create_date.
How we handle it
To preserve Act!'s original timestamps on mail.message and mail.activity, we use raw SQL post-load to backfill the date field (XML-RPC doesn't accept create_date on insert). This requires database write access during the migration window.
Deployment model (Cloud vs Desktop) drives extraction approach
Same as all Act! migrations: Cloud uses Web API, Desktop typically uses SQL Server read access.
How the migration runs
Discovery + Odoo edition confirmation
Confirm Act! deployment, Odoo edition (Community vs Enterprise vs Online), and which Odoo apps are installed (CRM only vs CRM + Sales + others). Inventory custom fields, Groups, Custom Tables, Documents.
Odoo pre-flight
Deploy Studio or custom modules for Custom Tables, configure crm.stage records for pipeline mapping, set up res.partner.category tags for Group equivalents, ensure Sales app is installed if Opportunity Products are in scope.
Sample + customer review
Migrate 50 Companies, 200 Contacts (linked to companies), 30 Opportunities with Products, 100 mail.activity, 500 mail.message. Customer reviews partner-model conversion fidelity.
Full extraction + Document download
Bulk Act! extraction. Documents download in parallel.
Full load via XML-RPC + SQL backfill
Bulk load Companies (res.partner is_company=True) → Contacts (res.partner parent_id) → crm.lead → sale.order with lines → mail.activity → ir.attachment. SQL post-pass to backfill timestamps on mail.message.
Cutover + decommission
Delta sync on cutover day. Sales reps switch to Odoo. Act! read-only for safety window.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
Odoo migrations carry partner-model conversion overhead plus Studio/custom-module deployment for Custom Tables. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Act! to Odoo CRM →Why teams move from Act! to Odoo CRM
- Odoo's modular suite (CRM + Sales + Inventory + Accounting + Project + ~80 more apps in one database) is the structural draw for Act! customers expanding beyond contact management. Teams that bought Act! when they only needed CRM and now want unified sales + inventory + accounting choose Odoo for the all-in-one model.
- Odoo Community Edition is free and self-hostable — appealing to customers leaving Act! Premium Desktop who want to retain on-premise control without per-seat licensing. Odoo Enterprise at $31/user/month is competitive with Act!'s pricing while delivering vastly broader functionality.
- Odoo's XML-RPC and JSON-RPC APIs, plus the Odoo Studio low-code customization tool, give customers automation and customization depth that Act! lacks without third-party add-ons.
- Open-source roots and active community give Odoo a meaningful module marketplace (apps.odoo.com) where SMBs can extend CRM functionality without bespoke development — a contrast to Act!'s narrow ecosystem.
- Self-hosting capability with full SQL access (PostgreSQL) preserves the on-premise architecture preference of Act! Desktop holdouts while removing the Windows + IIS + SQL Server stack maintenance burden — Odoo runs on Linux + Python + PostgreSQL.
Questions, answered
Act! to Odoo CRM migration questions
How does Odoo's unified partner model affect my Act! data?
Act!'s separate Contact + Company tables both become res.partner rows in Odoo, differentiated by an is_company flag. We set parent_id on Contact partners to point at their Company partner so the parent-child relationship is preserved. Filters, reports, and the Odoo UI handle the unified model naturally — but customers familiar with Salesforce or HubSpot sometimes find it surprising.
Does Odoo Community support Act! Custom Tables?
Yes, but Community requires a custom Python module deployed to the Odoo addons path (no Studio low-code in Community). We deliver a custom module zip during pre-flight that the Odoo admin installs and restarts the server. Enterprise users get Studio-based deployment instead — same data model, simpler delivery.
Where do Act! Opportunity Products end up in Odoo?
As sale.order.line records on a draft sale.order linked to the Opportunity (crm.lead). This requires Odoo's Sales app installed. If you don't run Sales, we serialize the product list as a JSON note on the Opportunity instead.
What happens to Act! Documents in Odoo?
Upload as ir.attachment records linked to the parent res.partner or crm.lead. Storage location depends on your Odoo configuration — either in the database as base64 or in the filestore directory. Either way, attachments render in the Odoo UI under the parent record's Documents tab.
Can Act! and Odoo run in parallel during migration?
Yes. Extraction is read-only against Act!. Cutover day catches deltas. Odoo Online (SaaS), Odoo.sh (PaaS), and self-hosted Community/Enterprise all support parallel-run setups during the safety window.
How are Act! Activity Series handled?
Expand within agreed active window (typically next 12 months + last 24 months historical) as individual mail.activity records. Recurrence rule preserves as a custom field for re-creation in Odoo's calendar if needed.
Related migrations
Odoo implementation
Set up Odoo CRM and migrate into it as one engagement.
See the service → MyCase to Odoo CRMMapping · history · rollbackDynamics 365 to Odoo CRMMapping · history · rollbackFlowlu to Odoo CRMMapping · history · rollbackZendesk Sell to Odoo CRMMapping · history · rollbackSuiteCRM to Odoo CRMMapping · history · rollbackMailchimp to Odoo CRMMapping · history · rollback Act! to SalesforceMapping · history · rollbackAct! to Zoho CRMMapping · history · rollbackAct! to HubSpotMapping · history · rollbackSources: official documentation
- Export and import data — Odoo 19.0 documentation
- Import products — Odoo 19.0 documentation
- Odoo Online programmatic throughput limits — Odoo Forum
- Data Cleaning — Odoo 19.0 documentation
- Datetime field reference — Odoo 19.0 documentation
- Upload size limit in Odoo — Odoo Forum (128 MiB cap)
- Fields and widgets — Odoo 19.0 documentation (Studio)
Get a quote
Moving from Act! to Odoo CRM?
Tell us roughly how many records and objects you have. We scope the mapping and the Odoo CRM setup with you, then send a quote.
Get a quote