Migrate from Deskera ERP to Infor CloudSuite Corporate

Deskera stores the COA with account codes, names, and standard types (Asset, Liability, Equity, Revenue, Expense) plus optional dimensions (Class, Location, Department). We export the full COA from Deskera via the /v1/accounting/chartOfAccounts endpoint, validate account code uniqueness, and map each account to the corresponding CloudSuite accounting table using the migration utility's source table definition. Deskera dimension assignments (Class, Location, Department) map to CloudSuite Cost Element or Analysis dimension fields if the customer has CloudSuite Financials configured for multi-dimensional accounting.

Deskera customer records (fetched via /v1/account with type filter) include billing address, shipping address, contact name, email, phone, currency, credit limit, and tax ID. We separate customer from vendor records during export to avoid cross-contamination of party data. In CloudSuite, customers are created with the customer number, name, address, and payment terms. Customer-specific pricing rules migrate as price book entries or customer-specific discounts configured in CloudSuite Financials.

Vendor records share the same Deskera /v1/account endpoint with a type=vendor filter. We extract vendor name, address, contact, bank details, W-9 status, and payment terms. In CloudSuite, vendors require a vendor number, name, address, and remittance information. 1099 reporting fields from Deskera map to CloudSuite vendor tax and reporting attributes.

Historical journal entries from Deskera include the journal date, entry description, account reference, debit or credit amount, and optional dimensions. We flag whether the customer wants full historical migration (typically 1-2 years retained online) or selective migration of open-period entries only, since CloudSuite's transactional database has storage implications for multi-year history. Open period entries migrate as open GL transactions; closed period entries migrate as locked historical records. Infor's Data Lake option is recommended for full history retention outside the transactional database.

Deskera inventory items include SKU, item name, unit of measure, cost, on-hand quantity, reorder point, and lot/serial tracking settings. We migrate item records and the current on-hand quantities from Deskera's stock module. Lot and serial data migrates as Inventory Lot and Serial Number records in CloudSuite's lot/serial tracking tables if enabled. Item costing method (standard, average, FIFO) maps to the corresponding CloudSuite costing policy.

Open sales orders from Deskera migrate to CloudSuite with customer linkage, order date, requested delivery date, line items (item, quantity, unit price, discount), and tax. We migrate open orders only; closed or invoiced orders migrate as historical records or remain in Deskera as read-only historical reference per the customer's cutover date decision. Deskera's order-to-invoice workflow differences from CloudSuite's pipeflow are documented for the customer's admin to review post-migration.

Open purchase orders migrate with vendor linkage, expected receipt date, line items, and quantities. Closed historical POs require a scope decision: migrate as historical records or archive outside CloudSuite. CloudSuite's PO workflow (approval hierarchy, receipt matching) differs from Deskera's; we document the workflow delta for the customer's Infor partner to configure post-migration.

Deskera MRP multi-level BOMs are extracted as assembly-component records with quantities-per-assembly. CloudSuite Industrial (SyteLine) natively supports multi-level BOMs and routings, so the Deskera BOM structure maps to CloudSuite's BOM and Routing tables. Component items, quantities per assembly, operation sequences, work centers, and labor/burden rates migrate as configured. If the destination is CloudSuite Distribution (without MRP), we extract BOM structures as flat item-association records and flag this for manual reassembly.

Deskera People (HRMS) stores employee records with name, department, compensation, leave balances, and organizational hierarchy. We migrate core employee fields (name, ID, department, job title, hire date, employment status). Effective-dated payroll history requires additional mapping to CloudSuite Human Capital Management or Infor HCM; if the customer does not license Infor HCM, we migrate the employee master without payroll history and flag the gap for the customer's HRIS decision.

Deskera CRM contacts exist within the integrated CRM module and link to accounts. Custom contact properties and lifecycle stages migrate as custom fields in CloudSuite CRM or as attributes on the Contact object. Contact ownership (assigned user) maps to the CloudSuite user who will own the contact post-migration.

Deskera supports custom field creation on most objects. We capture custom field definitions (field name, data type, required/optional) and their values per record. In CloudSuite, custom fields are created as user-defined fields on the corresponding tables. We pre-create the destination schema with matching custom field names and types before any data import. Custom field mapping is validated during the sandbox migration pass before production cutover.