Migrate from Flectra to Infor CloudSuite Corporate

Flectra res.partner records where is_company is false map to Infor CloudSuite Contact Management. We extract name, email, phone, street, city, country, and the parent_id link to the company partner. The Infor Contact Management module stores contact roles, communication preferences, and address hierarchies that parallel Flectra's partner model. Any x_ custom fields on the Flectra contact record are enumerated during discovery and mapped to Infor OS Data Model extensions configured before import.

Flectra res.partner records where is_company is true map to Infor CloudSuite Customer Management. We extract company name, website, vat, and the child_ids relation back to individual contacts. Infor CloudSuite's Customer Management holds credit limits, payment terms, and Tax ID registration that must be populated as part of the import. Tax registration numbers from Flectra's partner records require format validation against Infor's country-specific tax ID rules before load.

Flectra sale.order and its sale.order.line records map to Infor CloudSuite Sales Order Management. We extract order reference, partner_id (Customer link), order date, line-level product, quantity, unit price, and tax. Open sales orders migrate as active records; confirmed, locked, or cancelled orders migrate as historical records with status preserved. The Infor Sales Order Management module requires a valid Customer link and Product link before order lines can be created, enforcing the import sequencing constraint.

Flectra account.move records with move_type=out_invoice map to Infor CloudSuite Financial Management invoices. Flectra's payment_state field (state_posted vs state_pending) requires explicit mapping to Infor's invoice status values. Posted invoices migrate with their full line distribution and tax lines. We scope the historical invoice window during scoping: CloudSuite Financials is not optimised for unlimited transaction history, and we recommend migrating one to two years of posted invoices with older records archived to Infor Data Lake for reporting.

Flectra purchase.order and purchase.order.line map to Infor CloudSuite Purchase Management. We extract vendor reference, order date, line-level product, quantity, and cost price. Open purchase orders migrate as active records; received or invoiced purchase orders migrate as historical with receipt status preserved. Infor Purchase Management requires a valid Vendor (Customer with Supplier role) link, which we resolve during the Customer import phase before purchase order loading begins.

Flectra's two-level product model (product.template as the master and product.product as variants) maps to Infor CloudSuite Product Data Management. We extract product.template fields (name, type, categ_id, list_price, standard_price) and the variant attributes (product.attribute.value_id combinations) as separate variant records. The template-to-variant relationship is preserved so that variant-level pricing and BOM data load under the correct parent product. Products without variants are imported as single records without a variant layer.

Flectra project.project and project.task map to Infor CloudSuite Project Planning and Task Management via Infor OS. We extract project.name, project.user_id (assignee), project.stage_id, task.name, task.user_id, task.planned_hours, task.effective_hours, and the task.child_ids sub-task hierarchy. Infor OS Project Planning is a separate module from the core ERP and must be licensed and provisioned before task data can load; we confirm module availability during discovery.

Flectra hr.employee records map to Infor CloudSuite HR Employee Central. We extract name, department_id, job_id, work_email, and work_phone. Flectra's bank_account_id field for payroll details does not migrate; payroll and benefit data typically resides in a dedicated payroll module that sits outside the standard ERP migration scope. We flag any hr.employee records with active project assignments so those project-task links can be verified post-migration.

Flectra ir.attachment records (binary files linked via res_model and res_id) are exported as base64-encoded blobs. We re-attach them in Infor CloudSuite Document Management by resolving the res_model and res_id to their Infor equivalents after the parent records have loaded. Attachments on sale.order map to Sales Order documents; attachments on account.move map to Financial Management document records. Any attachment without a resolvable parent record is held in a reconciliation queue for manual handoff.

Flectra custom fields defined in ir.model.fields with state=manual and the x_ prefix are enumerated during discovery via a schema introspection script. For each x_ field we identify the target Infor object, the appropriate Infor OS Data Model extension type (string, number, date, picklist), and whether the extension must be deployed to a Sandbox before record import can proceed. Custom field mapping is validated in the staging environment before production migration begins. Fields with complex data types (relational, computed) are flagged for manual post-migration configuration.