Migrate from weclapp erp to Odoo ERP

weclapp Customers map to Odoo private addresses on the res.partner record. weclapp stores name, address, email, phone, tax ID, and payment terms; Odoo splits these into Contact (address data) and the partner itself. The weclapp customer number becomes the partner's ref field for dedupe. Tax ID from weclapp maps to Odoo's vat field for EU VAT validation. Customer type (company vs individual) sets the Odoo partner's is_company flag.

weclapp Company records (B2B accounts distinct from individual contacts) map to Odoo commercial partners with is_company=True. The weclapp company address, website, industry, and employee count map to equivalent Odoo partner fields. When a weclapp Company has linked weclapp Contacts, those map to Odoo private addresses attached to the commercial partner. Company is created before any contact import so the parent link is satisfied at insert time.

weclapp Items (products and services with SKU, description, unit price, stock quantity) map to Odoo Product Template records. weclapp pricing tiers per customer group map to Odoo Pricelist entries attached to the Product Template. Stock quantities on hand transfer to Odoo quants in the default warehouse location. weclapp Items with variant attributes (size, color) generate Odoo Product Variants through the attribute configuration. Service items without stock tracking map to Product Template with type=service.

weclapp Sales Orders with linked Customers and Items map to Odoo sale.order with sale.order.line records. The weclapp order status (Draft, Confirmed, Delivered, Invoiced) maps to Odoo's state field (draft, sale, done, cancel). Historical closed orders export as read-only Odoo sale.order records. Order dates, shipping addresses, and payment terms migrate. weclapp's sales representative assignment maps to Odoo's user_id on the order header.

weclapp Purchase Orders map to Odoo purchase.order with purchase.order.line records. Linked vendor records from weclapp map to Odoo supplier partners (supplier rank > 0). Line items preserve quantity, agreed unit price, and product link. Purchase order status from weclapp maps to Odoo's state field (draft, sent, purchase, done, cancel). Dates and the assigned buyer user migrate to Odoo's date_order and user_id respectively.

weclapp Sales Quotations map to Odoo sale.order in draft state (Odoo uses the same model for both quotes and confirmed orders, differentiating by state). The weclapp validity date maps to Odoo's validity_date field. Pricing and line items transfer directly. Once a weclapp quote is Accepted, it migrates to Odoo sale state; if it remains open, it stays in draft state as a quotation. Customer signature or acceptance records do not carry over as Odoo does not store a separate signed-document record natively.

weclapp Invoices map to Odoo account.move of type out_invoice (for customer invoices) or in_invoice (for vendor bills). Line items, tax codes, payment terms, and invoice status migrate. Paid and closed weclapp invoices migrate as Odoo posted (locked) records and must not be re-activated to prevent double-posting in financial reports. weclapp's DATEV export fields (tax rates, account codes) are noted in the mapping but Odoo does not have native DATEV export — this requires a separate DATEV-compatible accounting module or custom development post-migration.

weclapp Projects with nested Tasks and optional time entries map to Odoo project.project and project.task. The weclapp project status workflow (active, completed, archived) maps to Odoo's active and stage_id fields. Project manager assignment migrates to Odoo's user_id on the project header. Time entries on weclapp tasks map to Odoo account.analytic.line (timesheet entries) linked to the task if the Timesheets app is installed. Project billable flag from weclapp Services plan maps to Odoo's allow_billable setting.

weclapp Documents attached to Customers, Companies, Orders, Invoices, and Projects export as binary blobs. We re-upload them to Odoo as ir.attachment records linked via res_model and res_id to the corresponding Odoo record (res.partner, sale.order, account.move, project.project). Original filenames and MIME types are preserved. Odoo's attachment storage backend (database or file system) is set during Odoo installation and affects how we configure the upload endpoint during migration.

weclapp custom fields on Customers, Companies, Items, Orders, and Projects are enumerated during discovery by querying object metadata per-type (there is no single discovery endpoint in weclapp's API). We create equivalent custom fields in Odoo via developer mode or the settings UI, with Salesforce-style __c API names, before record import. Custom field type mapping: weclapp text maps to Odoo char or text depending on length; weclapp date maps to Odoo date; weclapp number maps to Odoo float or integer; weclapp dropdown maps to Odoo selection. Any custom fields with no Odoo equivalent are flagged for manual re-entry or custom field creation.

weclapp Helpdesk Tickets (available on plans with the Helpdesk add-on) map to Odoo helpdesk.ticket if the Helpdesk app is installed, or to project.task in a dedicated helpdesk project if the app is not in scope. Ticket status, priority, linked Customer, assigned Agent, and conversation threads export. Conversation threads map to Odoo mail.message records linked to the ticket. The Helpdesk add-on must be confirmed active in weclapp during scoping — if absent, tickets are not present in the export and scope is adjusted accordingly.

weclapp Contract Management add-on records (available on certain plans) link to Customers and carry contract terms, start/end dates, and renewal details. These map to Odoo sale.subscription (for recurring service contracts) if the Subscription app is installed, or to account.move records for one-time contracts. Linked contract documents migrate as ir.attachment. If the Contract Management add-on is not active on the source weclapp plan, contract records are absent from export and this object is removed from migration scope.