Migrate from Spectrum ERP to Microsoft Dynamics 365 Business Central

G/L Account web service with Excel template enables bulk chart-of-accounts import from Spectrum. Account structure (segments, rollup hierarchies) maps to the destination account structure via a pre-migration mapping session. We preserve account numbers, descriptions, account type (P&L vs. balance sheet), and any sub-account segments. The destination segment configuration must be finalized before journal entry import because account codes are referenced in every journal line.

Spectrum Jobs with Phases and Cost Codes map to Dynamics 365 Projects with WBS levels. We map Job to Project header, Phase to WBS task level, and Cost Code to Project Category or Dimension value depending on the destination edition configuration. Historical job cost totals are preserved by migrating completed job transactions as historical project transactions with actual costs posted. The destination project structure (flat vs. hierarchical WBS) is decided during scoping based on the customer's reporting requirements.

Work orders link to Jobs and carry labor, materials, and equipment allocations. We preserve the work order-to-job linkage by resolving the destination Project reference at migration time. Labor lines map to project time entries; material lines map to item consumption lines; equipment lines map to resource entries. Associated notes and images transfer via the Document Imaging web service. Work order status (open, closed, invoiced) maps to the destination work order status field.

Customer records from Spectrum's A/R module migrate to Dynamics 365 Customer records. We preserve customer name, address, contact information, payment terms, credit limits, and tax registration numbers. Open A/R invoices migrate as open customer ledger entries with remaining amounts. Historical paid invoices migrate as closed ledger entries for audit trail completeness. Customer-specific GL posting assignments map to Business Central or Finance & Operations business posting groups.

Vendor records from Spectrum's A/P module migrate to Dynamics 365 Vendor records. We preserve vendor name, address, contact information, payment terms, W-9 data, and 1099 flag. Open A/P invoices migrate as open vendor ledger entries. Historical paid invoices migrate as closed entries. Vendor-specific posting assignments map to vendor posting groups in the destination. 1099 reporting fields carry over from Spectrum's vendor records to the equivalent Dynamics 365 fields.

Journal entries are migration-critical: both sides of every entry must land in Dynamics 365 together or the trial balance will not reconcile. We extract both debit and credit lines from Spectrum's Add G/L Journal Entries web service in a single call per entry, preserving account code, amount, description, and posting date. The destination journal batch is created before line import, and we map Spectrum cost code assignments to the destination project or dimension value. We run a trial balance validation after journal import to confirm that total debits equal total credits in the destination.

Employee records, dependents, insurance, and training certifications migrate via Spectrum's web services. We map employee name, address, employment status, pay groups, and direct deposit information. Certified payroll compliance fields (union agreements, prevailing wage rates, Davis-Bacon flag) are extracted during scoping and handed off as a payroll configuration brief for the customer's Dynamics 365 partner. Deduction codes, benefit enrollment, and training certifications require customer-specific remapping because union rules and benefit structures vary by project and state.

Construction payroll is one of Spectrum's strongest modules, supporting union rules and certified payroll with multi-union rule configurations. Pay stubs, pay groups, and deductions migrate as historical payroll records, but certified payroll and union rule compliance fields require destination payroll configuration before historical data is meaningful. We migrate payroll register data as general journal entries to preserve the financial impact, and we deliver a written payroll configuration brief identifying every deduction code, fringe benefit pool, union agreement, and prevailing wage rule requiring setup in Dynamics 365.

Equipment Tracking Requisition and Equipment Work Order web services support Excel template bulk import from Spectrum. Preventive maintenance schedules, work order components, equipment notes, and usage history migrate to Dynamics 365 Resources or Fixed Assets depending on the destination configuration. Equipment-to-project assignment links preserve the relationship between equipment records and the Jobs or Projects they are assigned to. If the destination uses Asset Management (Finance & Operations), equipment migrates to Fixed Assets with maintenance schedules preserved.

Inventory items from Spectrum's Inventory module migrate to Dynamics 365 Items with item type (inventory, service, non-inventory), unit of measure, cost method, and reordering policy preserved. Item-specific GL posting accounts map to inventory adjustment and variance accounts in the destination. Open purchase orders and sales orders migrate as open purchase and sales documents if the destination supports the same document structure, or as historical transactions if the destination order management module requires re-entry.

Project Log Images, Work Order Images, and Employee Images are available via dedicated Spectrum web services without Excel template support. Binary image data requires a separate transfer pass after relational records are in place. Images land in Dynamics 365 as attached documents on the parent record (project, work order, employee) or in Azure Blob Storage linked via a URL field. We preserve the association to the parent record by resolving the destination record ID before the image attachment pass.

Service Request custom fields are limited to four per form in Spectrum's Service Hub. We extract all four-field configurations during scoping, including field name, data type, and current values. In Dynamics 365 Business Central, we map these to custom fields on the equivalent entity using AL extensions. Where the destination allows more than four custom fields, we carry over the full set; where the destination has a comparable four-field limit, we preserve all four. Any Service Hub-specific field types (dropdown, checkbox, date) are mapped to the equivalent Dynamics 365 field type.