Migrate from daftra to Infor CloudSuite Corporate

Daftra Clients include both customers and suppliers under a single object. We split by Daftra client type flag: Customer-type clients map to Infor Customer records (custMstr), Supplier-type clients map to Infor Supplier records (suppMstr). Contact details, addresses, and follow-up history migrate as related Contact and Address records. Client membership points and insurance references preserve as supplementary properties noted for manual entry in Infor OS or the appropriate Cloudsuite module.

Daftra Products and Services catalog maps to Infor Item Master (ItemMstr or its equivalent in the applicable Cloudsuite edition). SKU (hs_sku), pricing tiers, stock levels, and supplier links migrate as item attributes. Product type (good vs service) maps to Infor Item Type. Custom fields on Daftra Products are enumerated and mapped to Infor extended data structures or user-defined fields on the Item form.

Daftra Invoices map to Infor Accounts Receivable invoices (customer invoices) or Accounts Payable vouchers (supplier invoices) depending on the Daftra invoice type flag. Line items, taxes, installment schedules, and sales commission assignments migrate as invoice lines and tax distributions. Custom fields on Daftra Invoices require per-field mapping to Infor extended fields or remark records. Invoice balance and payment status preserve for open invoice handling at cutover.

Daftra Expense records map to Infor expense or purchasing modules depending on whether the expense is internal (HRM) or payable to a vendor (AP). Amount, category, date, and attachment references migrate. We link expenses against the Infor Chart of Accounts using the account mapping established during COA load. Recurring expense patterns flag as a boolean on the Infor record for manual configuration of recurring voucher setup.

Daftra's Chart of Accounts exports as a flat table with parent-child relationships inferred from account codes. We reconstruct the hierarchical account tree during discovery, then load accounts to Infor in account code order to respect hierarchical posting sequence. Account type (asset, liability, revenue, expense) maps to Infor account category. Sub-account parent references populate using Infor's segment structure or hierarchical account linkage depending on the Cloudsuite edition's COA model.

Daftra Cost Centers map to Infor's cost center or department dimension (specific object name varies by Cloudsuite edition). The linking between Cost Centers and individual transactions requires field-level extraction from Daftra's expense and invoice records and mapping to Infor's dimension assignment fields. If Infor uses a multi-dimensional COA, Cost Centers become a dimension segment; if Infor uses a flat COA with cost center as a field, we configure the field mapping accordingly during discovery.

Daftra Employee records map to Infor Employee or Workforce Management records (specific object varies by Cloudsuite edition). Organizational structure placement, contracts, and attendance history migrate as employment records and related notes. Daftra payroll compensation time-series extracts as a separate payroll history file and loads to Infor HR as historical compensation records. Employee custom fields require per-field mapping to Infor HR extended fields.

Daftra Fixed Assets map to Infor Fixed Asset records. Asset master data (description, classification, acquisition date, cost) migrates as the asset header. Depreciation schedules extract from Daftra's Assets module separately and load as depreciation method and schedule records in Infor. Custom fields on Daftra Assets are enumerated per object and mapped to Infor fixed asset extended fields.

Daftra Work Orders map to Infor Production Orders (for manufacturing Cloudsuite editions) or Service Orders (for service management configurations). Work Order header data (client link, employee assignment, product link, status, stage history) migrates as order records with activity log preserved as notes or attachments. File attachments and linked documents migrate as ContentDocument records attached to the Infor order.

Daftra Reservation Files (PNR-style booking records) map to Infor reservation or appointment records where the applicable Cloudsuite edition supports service reservation management. Status tracking, appointment scheduling, and activity logs migrate as reservation header and line activity records. If the target Infor edition does not include native reservation management, we migrate reservation data as Work Order or Service Order records with a reservation flag for manual reorganization.

Daftra Cheque Cycle records track cheques through issue, deposit, and return stages tied to both the Chart of Accounts and specific invoice or payment records. We extract the full cycle history as a transaction supplement and link to the corresponding Infor AP or AR records created during invoice migration. Stage history (issued, deposited, returned, cleared) maps to Infor payment status fields or remark records. If the target Infor edition does not include a native cheque cycle tracker, we document the mapping for manual configuration in Infor Payments or AP module.