Migrate from Deskera ERP to Microsoft Dynamics 365 Business Central

Deskera stores the COA with account codes, names, and standard account types. We map account codes and names directly into the Dynamics 365 Chart of Accounts, preserving account types (Asset, Liability, Equity, Revenue, Expense) and any posting definitions. Deskera's dimension structure (Class, Location, Department) maps to Dynamics 365's financial dimensions; we configure the dimension set in the destination before any journal entry import. If Deskera uses a different account code length than the destination's account format, we pad or truncate during the transform step.

Deskera Customer records (fetched via /v1/account with type filter) include billing address, shipping address, payment terms, and credit limits. We map these to Dynamics 365 Customer records, splitting billing and shipping into separate Address records. Customer posting groups from Deskera map to Dynamics 365 Customer Posting Groups for receivables configuration. If the destination is Business Central, we also create a corresponding Contact record linked to the Customer for CRM touchpoints.

Deskera Vendor records use the same /v1/account endpoint with a vendor type filter, separating them from Customer records during scoping to avoid party cross-contamination. Vendor payment terms, bank details, and posting groups map to Dynamics 365 Vendor posting groups for payables configuration. If Deskera stores vendor-specific tax information (tax registration numbers, tax group assignments), these migrate as custom fields on Vendor.

Historical journal entries in Deskera store account references, debit/credit amounts, optional dimensions (Class, Location, Department), and posting dates. We map these to Dynamics 365 General Journal lines, resolving the Deskera account code to the destination G/L Account number at migration time. The mapping preserves the journal batch name, posting date, and document number for audit trails. Closed or locked Deskera periods require the destination fiscal year to be open for the corresponding date range before journal import begins.

Deskera Items store SKU (hs_sku equivalent), name, unit of measure, cost method, and on-hand quantities. We map these to Dynamics 365 Item records with the matching inventory posting group. Deskera's batch/lot and serial tracking options migrate as lot number and serial number tracking configuration on the Item. On-hand quantities import after the warehouse setup is validated in the destination so that inventory簿 entries are created against the correct location.

Deskera Sales Orders link to Customers, Items, and pricing rules with line-level quantities, unit prices, and discount amounts. We migrate open orders with status preserved so that partially fulfilled orders continue as open in Dynamics 365. Deskera's order-to-invoice workflow (which may differ from Dynamics 365's warehouse shipment and invoicing cycle) is documented in the mapping notes; the customer's admin configures the fulfillment workflow post-migration. Closed historical orders migrate as sales history if the customer specifies an accounting cut-off date.

Open Purchase Orders in Deskera migrate with vendor linkage, expected receipt dates, and line-level items. We preserve the receipt status so that partially received POs continue as open in Dynamics 365. Closed historical POs migrate selectively based on the customer's cut-off date for open item reporting. If Deskera uses multi-warehouse receipts, the vendor warehouse assignment maps to a Dynamics 365 location.

Deskera MRP supports multi-level BOMs with component items, quantities per assembly, and routing steps. Dynamics 365 does not replicate this structure identically: Business Central requires the Manufacturing extension for BOM support, and Finance and Supply Chain Management requires Production Control. We extract BOM structures as flat item-association records with parent component and quantity relationships, then flag the discrepancy in the mapping notes so the customer's manufacturing consultant can reassemble routing logic, work centers, and capacity planning in the destination MRP module post-migration.

Deskera People stores employee records with compensation, leave balances, organizational hierarchy, and employment status. We migrate core employee fields (name, employee number, hire date, department, job title, reporting manager) to Dynamics 365 Human Resources Worker records. If the destination is Business Central without the HR module, we migrate employee records as Contacts with a custom Employee flag. Effective-dated payroll history requires additional mapping beyond standard migration scope and is flagged for the customer's HR implementation partner. Leave balances migrate as Dynamics 365 absence registration entries if the HR module is licensed.

Deskera CRM Contacts exist within the integrated CRM module and link to Company (Account) records. Custom contact properties and lifecycle stages migrate as custom fields in Dynamics 365 where direct field mapping is not available. We preserve the contact's email address, phone, address, and any owner assignment from Deskera, mapping the owner email to a Dynamics 365 User record.

Deskera's multi-currency support with user-defined decimal precision for exchange rates maps to Dynamics 365's Currency page and Exchange Rate Provider setup. We migrate the currency list, exchange rate decimal precision, and any manual exchange rates as of the migration snapshot date. If Deskera uses a specific base currency, we configure the same as the Dynamics 365 general ledger setup base currency.

Deskera supports custom field creation on most objects. We capture custom field definitions (field name, data type, required flag) and their values per record during export. In Dynamics 365, these become custom fields added via extensions (AL extensions in Business Central, Power Apps field customization in Finance and Supply Chain Management). We pre-create the destination schema for custom fields before data import so that values land in typed fields rather than generic supplementary lookup tables.