Migrate your Deskera ERP data

Deskera stores the COA with standard account types and supports export to PDF, XLSX, and CSV. We map account codes and names directly into the destination COA, preserving account types and tax codes where present.

The /v1/account endpoint handles both create and fetch operations. We pull all customer records including billing/shipping addresses and contact details, then map them to the destination's equivalent company or contact object.

Vendor data is available via the same account API with a type filter. We separate vendor from customer records during migration scoping to avoid cross-contamination of party records.

Historical journal entries can be exported individually. Deskera stores journal lines with account references, debit/credit amounts, and optional dimensions (Class, Location, Department). We map these line-by-line but flag dimensions that may not exist in the destination system.

Items include SKU, name, unit of measure, cost, and on-hand quantities. Deskera supports batch/lot and serial tracking. We migrate item records and option to include lot/serial data depending on the destination's capabilities.

Sales orders link to customers, items, and pricing rules. We migrate open orders and preserve line-item pricing but note that Deskera's order-to-invoice workflow may differ from the destination's pipeline stages.

Open purchase orders are migrated with vendor linkage and expected receipt dates. Closed historical POs may require selective migration based on the customer's accounting cut-off requirements.

Deskera MRP supports multi-level BOMs for manufacturing. We extract BOM structure, component items, and quantities per assembly, but mapping to a destination with a different MRP engine requires manual review of routing and work center definitions.

Deskera People (HRMS) stores employee records with compensation, leave balances, and organizational structure. We migrate core employee fields; effective-dated payroll history requires additional mapping to the destination's payroll schema.

Contacts exist within the integrated CRM module and link to accounts. Custom contact properties and lifecycle stages are preserved as custom fields in the destination where direct mapping is not available.

Deskera supports custom field creation on most objects. We capture custom field definitions and their values per record, storing them as destination-native custom properties or in a supplementary lookup table.