Migrate from Flectra to Microsoft Dynamics 365 Business Central

Flectra Contacts (res.partner with is_company=False) map directly to Dataverse Contact. The Flectra name field maps to fullname; email, phone, street, city, state, zip, country map to corresponding Contact fields. We resolve parent_id (the link to the Flectra company record) to the D365 Account ContactId during import. Address data in Flectra's partner fields maps to postaladdress and composes into the Contact address composite field in D365.

Flectra Companies (res.partner with is_company=True) map to Dataverse Account. Fields including website, vat, industry_id, and comment transfer as Account Website, VAT, Industry, and Description. Flectra's child_ids relation (individual contacts belonging to the company) resolves to D365 Account's primarycontactid and the related contacts table. Company records are loaded before Contact records to satisfy the AccountId lookup requirement.

Flectra sale.order maps to D365 SalesOrderHeader (Business Central) or Opportunity (Sales module) depending on which D365 app is licensed. Order state, date_order (order date), and origin document reference transfer directly. Flectra's partner_shipping_id and partner_invoice_id map to D365 ship-to and bill-to address lookups. We preserve the confirmed date and any origin document reference for audit trail.

Flectra sale.order.line maps to D365 SalesOrderLine. Product ID resolves via SKU match to D365 Item Number; product_uom_qty maps to Quantity; price_unit maps to UnitPrice. Flectra's tax_id on the line maps to D365 tax group assignment. Line-level discount and description fields transfer to the corresponding D365 line discount and line description fields.

Flectra customer invoices (account.move with move_type=out_invoice) map to D365 SalesInvoice in Business Central or CustInvoiceJournal in Finance. Flectra's payment_state (posted vs pending) maps to D365 status with the document status preserved as a custom field for reconciliation. Invoice lines (account.move.line) map to D365 InvoiceLines with account_id mapping to the appropriate G/L account in D365.

Flectra's product.template holds the product master (name, list_price, categ_id, type). This maps to the D365 item master or product record. The template-to-variant relationship (product.product records linked via product_tmpl_id) maps to D365's product variants using the Dimension framework (size, color, etc.) or by creating separate product records for each variant. We preserve attribute values from product.attribute.line during the split so that variant descriptions are accurate in D365.

Flectra product.product records map to D365 product variants under the parent product.template master. We match on the combination of product attributes (attribute_id + value_id) to map to D365 Dimension values. Standard cost, lst_price, and seller_ids (vendor pricelists) transfer as variant-level pricing and vendor data. If D365 uses a flat product model, variants become separate product records with a custom parent_product__c lookup field.

Flectra purchase.order maps to D365 PurchaseOrder. Vendor (partner_id) resolves to the D365 Vendor Account. Order state (draft, sent, purchase, done, cancel) maps to D365 Status. Flectra's picking_ids (receipts linked to PO) map to D365 Receipts, though picking state may need to be reconstructed from Flectra's stock.picking records if PO and warehouse modules are active.

Flectra purchase.order.line maps to D365 PurchaseOrderLine. Product ID resolves to D365 Item Number via SKU match; product_qty and price_unit transfer directly. Flectra's date_planned maps to the D365 ExpectedReceiptDate. Taxes and discounts on the line map to D365 tax and discount fields on the purchase line.

Flectra project.project maps to D365 Project (Project Service Automation module or Business Central Projects). Project name, date, user_id (manager), and partner_id (customer) transfer as Project Name, StartDate, Project Manager, and Customer Account. Flectra's analytic_account_id maps to D365's analytical accounting structure if Finance is in scope.

Flectra project.task maps to D365 ProjectTask under the parent Project. Stage_id maps to D365 Task Stage; user_id (assignee) resolves via email to D365 Resource; planned_hours and effective_hours transfer as Planned Hours and Actual Hours. Sub-tasks (child_ids) nest via the Parent Task lookup field in D365 Project Service. If the Project Service Automation module is not licensed, tasks migrate to Dataverse Task with a custom project__c lookup.

Flectra hr.employee maps to D365 BookableResource (when Project Service Automation is in scope) or a custom Employee table in Dataverse. Fields including department_id, job_id, work_email, and mobile_phone transfer. Bank account details, emergency contact, and payroll data (if present in Flectra) migrate as custom fields or remain in Flectra HR if the HR module is not in scope for the D365 migration. Salary history typically resides in a separate payroll module not migrated.

Flectra ir.attachment records with res_model and res_id linking to business objects migrate as D365 Annotations. Files export as base64-encoded binary and load as D365 Note documentbody with the original filename and mimetype preserved. The res_model and res_id resolve to the target D365 table and record ID during import so that the annotation attaches to the correct object. Large attachments (>120MB) may require SharePoint document management configuration in D365.

Flectra custom fields (ir.model.fields with state='manual', x_name prefix) are enumerated during discovery via ir.model.fields reads through the XML-RPC API. We pre-create equivalent custom columns in the destination D365 Dataverse table using the column name with a __c suffix per Dataverse naming convention. Field type mapping: Char -> Text, Integer -> Whole Number, Float -> Decimal Number, Boolean -> Two Options, Date -> Date, Datetime -> Date and Time, Many2one -> Lookup, Many2many -> Multi-Select Option Set or related table. The mapping is validated in a Sandbox before production load.

Flectra fiscal positions (account.fiscal.position) with their account_mapping rules (source account to destination account) are mapped to D365 Tax configurations or G/L Account mappings depending on the D365 module in scope. Multi-currency exchange rates from res.currency.rate transfer to D365 Currency Exchange Rates. The fiscal year configuration (account.fiscal.year) maps to the D365 Fiscal Calendar setup. These are loaded as configuration data before transactional records to ensure tax and account references resolve correctly.