Migrate from Zenscale to Microsoft Dynamics 365 Business Central

Zenscale stores a hierarchical financial chart of accounts with cost-center tagging across the Financial Accounting module. We extract account codes, account names, account type (Asset, Liability, Income, Expense), and cost-center assignments, mapping them to Dynamics 365 Finance or Business Central G/L Account records with the same account structure. Zenscale's cost centers map to Financial Dimensions in Dynamics (such as Department or Cost Center dimension sets), which must be configured in the destination before account import so that posting configurations accept the incoming dimension values.

Zenscale maintains customer records with GST registration details (GSTIN), payment terms, credit limits, billing and shipping addresses, and contact information. We map these to Dynamics 365 Customer records, with GSTIN preserved in the Tax Identification Number field, payment terms mapped to Dynamics Payment Terms records, and credit limits transferred to the Customer Credit Limit field. Customer addresses map to the Dynamics Address and Contact information structured fields.

Zenscale supplier records include vendor name, PAN and TAN for Indian tax compliance, GSTIN, payment terms, credit limits, and address data. We map these to Dynamics 365 Vendor records, preserving PAN in the Tax Registration field, GSTIN in the Tax Identification Number, and payment terms to the corresponding Dynamics Payment Terms record. Zenscale's purchase price lists map to Dynamics Vendor Trade Agreements.

Zenscale item masters store finished goods, raw materials, and semi-finished items with BOM linkages, unit of measure, stock thresholds, and valuation methods (FIFO, Standard). We split this into Dynamics 365 Item records (product master with inventory dimension tracking), Bill of Materials (for FG and semi-finished items with BOM components), and vendor-specific trade agreements for raw materials. Item tracking dimensions (Batch, Serial, Location) must be configured in Dynamics before stock data imports to avoid validation rejections.

Multi-level BOMs and routing steps from Zenscale's Production Planning module map to Dynamics 365 Bill of Materials (BOM) versions and Production Route records. We extract BOM component quantities, consumption rates, and operation sequences from the production order export. BOM versions require version numbers and effective dates; routes require work center references and operation times. Zenscale's job work order data maps to Dynamics Subcontracting agreements or Purchase orders with BOM-linked components, depending on the destination configuration.

Zenscale production orders include routing steps, work-center assignments, BOM component consumption, and quantity with start and end dates. We map these to Dynamics 365 Production Orders with the same status (Created, Scheduled, In Process, Completed). We request a full production history export including closed orders to preserve BOM revision trails, because Zenscale's BOMs are versioned against production orders and the version lineage must transfer intact for costing and compliance reporting.

Zenscale open PO records with line-item pricing, delivery schedules, and GST tax components map to Dynamics 365 Purchase Orders. We extract pending order balances and map them to the destination's open purchase order documents, flagging any line items where the vendor or item cannot be resolved for manual review before import. Purchase order history (closed POs) migrates as invoice and receipt records if the customer requires audit trail continuity.

Zenscale open sales orders with line-item pricing, delivery schedules, and GST tax components map to Microsoft Dynamics 365 Sales Orders. We extract pending order balances and map them to the destination's open sales order documents, flagging any line items where the customer, item, or pricing cannot be automatically resolved. GST tax codes on sales orders map to Dynamics Tax Groups and Item Tax Groups configured for Indian GST.

Zenscale employee records include name, designation, department, employment type, and bank account details. We map these to Dynamics 365 Human Resources Worker records. Zenscale's cost center assignments on employees map to Worker dimensions in Dynamics for payroll cost allocation. If the destination is Dynamics 365 Finance without Human Resources, employees map to a Worker-type contact or custom employee table configured in the Finance company.

Zenscale stores salary components—Basic, HRA, allowances, deductions—alongside statutory contributions (PF, ESI, TDS) for Indian compliance. These map to Dynamics 365 Human Resources or to a third-party Indian payroll ISV integrated with Dynamics. We extract each salary component with its calculation rule and map to equivalent Pay Elements in the destination. Indian-specific components (PF Employer and Employee contributions, ESI, TDS) require configuration in the destination payroll setup before component import because they carry statutory rate dependencies and compliance reporting requirements.

Indian GST compliance data—GSTR-1 and GSTR-3B summaries and input tax credit registers—stored against transactions map to Dynamics 365 tax transaction records. We extract tax summary records and line-item GST amounts, flagging any mismatch between Zenscale's recorded GST and the calculated GST on imported transactions. Before migration, we validate Zenscale's GST summary against Form GSTR-2A to ensure no discrepancy exists, because Indian tax law holds businesses responsible for retrospective corrections on past returns.

Zenscale's quality management module stores inspection results linked to purchase orders and production lots, including pass/fail status, inspector names, rejection reasons, and corrective actions. We map these to Dynamics 365 Supply Chain Management Quality Orders, linking each quality order to the originating purchase receipt or production order. Quality associations must be configured in Dynamics before inspection records import so that the association type and sampling rules are available for linking.

Zenscale inventory ledgers contain current stock quantities, valuation methods, stock locations, and batch or lot numbers. We map these to Dynamics 365 Warehouse Management inventory on-hand entries and open inventory transactions. If Zenscale uses batch or serial number tracking, we configure those dimensions in Dynamics before stock data import. Valuation method (FIFO, Standard, Average) must match a configured Costing Version in Dynamics to avoid posting errors.

Zenscale stores attached documents—invoices, Goods Received Notes, quality certificates—in a proprietary file store without a publicly documented export API. We migrate document metadata (filename, document type, creation date, linked entity) as a record in a migration manifest. The customer configures a SharePoint or Azure Blob Storage integration in Dynamics post-migration and manually attaches or re-uploads documents as needed. We cannot extract binary attachment files from Zenscale without vendor-assisted database access.