Migrate from Solution ERP to Microsoft Dynamics 365 Business Central

Solution ERP account codes and hierarchies map to Microsoft Dynamics 365 Main Account records with Financial Dimension sets replacing cost-centre codes. We extract the full account catalogue including inactive accounts, then configure dimension sets in D365 using the source cost-centre codes as the Business Segment dimension. Gulf-specific VAT and excise tax codes (0%, 5%, 100%) require replacement with standard Sales Tax groups and Item Sales Tax groups configured for the applicable Gulf country (UAE, Saudi Arabia, Oman, Bahrain, Kuwait, or Qatar). The customer confirms the destination country tax regime before import begins.

Solution ERP Customer records map to D365 Customer with attached Contact records. Arabic company names are preserved in UTF-8 encoding; we validate that the destination D365 environment has the correct language pack and regional settings for RTL field rendering if Arabic remains the primary language. Payment terms, credit limits, and currency assignments transfer directly. Customer-specific tax ID numbers become Tax Exempt Number fields with the relevant exemption reason code.

Vendor master records transfer to D365 Vendor with Contact records. Tax registration numbers (TRN, VAT registration) become Tax Information fields on the Vendor. We validate IBAN and bank account formats against the destination country's banking standards, particularly for cross-border Gulf vendors. Multi-site vendors appearing once per site in Solution ERP are consolidated into a single Vendor record with multiple addresses in D365.

Items with pricing, stock levels, and unit-of-measure hierarchies require Unit of Measure translation between Solution ERP's naming conventions and D365's UOM schema. We extract the UOM catalogue during discovery and create a mapping table before migration. Items with Arabic descriptions are preserved in UTF-8 on the Product Translation page in D365. Construction-specific items (materials, labour, equipment hire) map to Product types that match the customer's cost category configuration.

Outstanding receivables and payables require careful date-range scoping around the migration cutoff. We extract open invoice numbers and match them to prevent duplication in D365. Partial payments spanning the cutoff date are flagged for manual allocation review. Post-date transactions are held in a staging table and imported after the go-live date with original posting dates preserved to maintain audit continuity.

Project records including budgets, milestones, and cost allocations transfer to D365 Projects. Construction-specific phases and billing schedules map directly to D365 Project phases and WBS (Work Breakdown Structure) lines. Cost-centre codes on project transactions become Financial Dimension values in D365, and we validate that the project cost category setup aligns with the destination's chart of accounts before migration. Open project transactions are migrated as pending project journal entries; completed projects migrate as historical records.

Solution ERP POS transaction logs require reclassification because they lack the COGS split needed for accurate financial posting in D365. We identify POS-specific transaction types during discovery, then split each transaction into a Sales Invoice record (revenue side) and a General Journal line (COGS side), applying the destination's COGS accounts during migration. POS transaction totals are validated against the migrated Sales Invoice totals as a reconciliation checkpoint before cutover.

Bank account balances and cash account records migrate to D365 Bank Account and the corresponding Ledger Account. We apply a migration-date cutoff balance adjustment journal entry to reconcile any transactions posted after the export snapshot. IBAN validation applies for cross-border accounts, and bank account currency is set to match the Solution ERP currency code.

Asset registers including acquisition dates, depreciation methods, and net book value transfer to D365 Fixed Assets. We validate depreciation schedules against destination tax depreciation rules for the applicable Gulf country. Assets under construction (AUC) map to the D365 Fixed Asset AUC setup, and we flag any assets with non-standard depreciation codes for manual review before import.

Historical vendor invoices migrate to D365 Vendor Invoice Journal with full line-item detail. We apply volume-based chunking for large invoice histories (typically more than 10,000 records) to respect D365 API batch limits. Original posting dates and financial periods are preserved to maintain audit continuity. Invoices with Gulf-specific tax codes are reclassified using the tax mapping table built during discovery.

Solution ERP attached files and document records require file-type filtering and metadata extraction separate from binary content. We extract document metadata (date, author, document type) as structured records and map them to D365's SharePoint/OneDrive document handling integration, which is the standard storage approach for Business Central and Finance and Operations. Binary content migration is scoped separately because document repositories vary by destination storage configuration.

User accounts and role assignments migrate as role-name mappings between Solution ERP's permission structure and D365 Security Roles. We flag admin-level accounts for explicit review and map active users to the appropriate D365 user licence tier (Team Member, Essentials, Premium). Inactive Solution ERP users are provisioned as inactive D365 users to preserve historical transaction ownership.

Custom properties on standard Solution ERP objects are exported as key-value pairs and mapped to D365 custom fields where supported. We create AL extension objects for each custom field using the destination environment's developer tools, and we flag any unsupported field types (such as file attachments or images stored as custom fields) for manual re-entry or alternative handling.

Solution ERP Work Orders for maintenance or service operations map to D365 Project Journal Lines if the destination is Business Central Projects, or to Service Orders if Service Management is licensed. We extract work order statuses, assigned technicians, and line-item details during discovery and map them to the applicable D365 service module during migration. Open work orders migrate as pending entries; completed orders migrate as historical records.