ERP migration
Field-level mapping, validation, and rollback between Syscom ERP and Microsoft Dynamics 365 Business Central. We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Business Central.
Syscom ERP
Source
Microsoft Dynamics 365 Business Central
Destination
Compatibility
11 of 12
objects map 1:1 between Syscom ERP and Microsoft Dynamics 365 Business Central.
Complexity
BStandard
Timeline
6-10 weeks
Overview
Moving from Syscom ERP to Microsoft Dynamics 365 is a structural migration that begins with extraction method selection, because Syscom ERP publishes no public REST or SOAP API. We work with the customer's IT team to run SQL exports from on-premise SQL Server deployments or coordinate partner API access for cloud-hosted environments, then map the extracted data into D365 Finance and Supply Chain Management (for large manufacturers) or Business Central (for mid-market distributors). Syscom's modular architecture means we inventory every active module during discovery to ensure BOMs, Work Orders, and multi-currency balances are not left behind. We do not migrate workflows, automations, or scheduled reports as code; we deliver a written inventory of every configured automation with its trigger, conditions, and recommended D365 equivalent for the customer's admin to rebuild. Historical transactional data and open-order status migrate fully; inventory transactions (movement history) are scoped separately based on reconciliation requirements.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Syscom ERP platform overview
Scorecard, SWOT, gotchas, and pricing for Syscom ERP.
Destination platform
Microsoft Dynamics 365 Business Central platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Business Central.
Data migration guide
The complete Dynamics 365 Business Central migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Dynamics 365 Business Central migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Business Central.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Syscom ERP object lands in Microsoft Dynamics 365 Business Central, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Syscom ERP
Item / Product
Microsoft Dynamics 365 Business Central
Released Product (Product Master)
1:1Syscom ERP item records (SKU, description, unit of measure, cost, and pricing tiers) map to D365 Released Products with a Product Master dimension group controlling inventory, purchase, sales, and storage dimensions. We preserve the source cost as the Active standard cost on the Released Product and flag any pricing tier records for migration as Sales Price or Purchase Price lines linked to the Trade Agreement Journal in D365.
Syscom ERP
Bill of Materials (BOM)
Microsoft Dynamics 365 Business Central
BOM and Formula (Production Bill of Materials)
1:1Syscom ERP BOMs with multi-level component hierarchies map to D365 BOM and Formula records with exploded BOM lines and version control. We extract the full BOM tree recursively, preserving parent-item references, quantity-per, operation-scrap percentages, and route links. Alternative BOMs map to D365 BOM versions with an active flag. BOM costing migrates to the Costing Version and Cost Group in D365 Finance.
Syscom ERP
Work Order / Manufacturing Order
Microsoft Dynamics 365 Business Central
Production Order
1:1Syscom ERP Work Orders map to D365 Production Orders. We extract production status (Scheduled, In Process, Completed), scheduled start and end dates, quantity, and the linked BOM and route references. Operation sequences from the source route map to D365 Job Card routes, and Work Order postings map to inventory posting profiles. Open Production Orders migrate with their current status preserved; closed orders migrate as production history.
Syscom ERP
Customer / Account
Microsoft Dynamics 365 Business Central
Customer
1:1Syscom ERP customer records (billing address, shipping address, contact details, credit limit, payment terms) map directly to D365 Customer with address roles, contact information, and a Customer Group assignment. We map the source credit limit to the Credit Limit field on the Customer and preserve any customer-specific pricing as a Trade Agreement record. Customer tax groups are assigned based on the shipping address jurisdiction.
Syscom ERP
Vendor / Supplier
Microsoft Dynamics 365 Business Central
Vendor
1:1Syscom ERP vendor records map to D365 Vendor with contact information, payment terms, bank details, and a Vendor Group assignment. We preserve vendor-specific notes as free-text fields on the Vendor record. Tax 1099 grouping and WITax code assignments are configured in D365 based on vendor country and type during the mapping phase.
Syscom ERP
Sales Order
Microsoft Dynamics 365 Business Central
Sales Order
1:1Syscom ERP Sales Order headers and lines migrate to D365 Sales Order with order number, customer reference, header-level charges, and line items (item number, quantity, unit price, line discount). We preserve open order status so that D365 flags which orders remain to be fulfilled and which are historical. Header and line notes migrate as Sales Order header and line text fields. Tax codes map from the source jurisdiction configuration.
Syscom ERP
Purchase Order
Microsoft Dynamics 365 Business Central
Purchase Order
1:1Syscom ERP Purchase Order headers and lines map to D365 Purchase Order with vendor reference, expected delivery date, line-item detail, and unit cost. PO status (Open, Received, Invoiced, Closed) is preserved in D365 so that partially received orders reflect their current fulfillment state. Line-item delivery schedules migrate to D365 Delivery Schedule lines if the customer uses multi-delivery date structures.
Syscom ERP
Inventory / Stock
Microsoft Dynamics 365 Business Central
On-hand Inventory (Inventory Dimensions)
1:1Current inventory balances migrate to D365 On-hand entries with Site, Warehouse, and Location inventory dimensions. We map Syscom ERP warehouse codes to D365 Warehouse and bin locations, preserving the physical location hierarchy. Inventory value migrates to the Stock Value report and is reconciled against the GL after migration. Historical inventory transactions (movement history) are not migrated by default; we scope this separately if the customer requires full transaction history in D365.
Syscom ERP
GL Chart of Accounts
Microsoft Dynamics 365 Business Central
General Ledger Account
1:1Syscom ERP chart of accounts (account codes, names, types, and parent hierarchy) maps to D365 Main Account with Financial Dimension structure. We preserve active versus inactive status and map the source account type (Asset, Liability, Equity, Revenue, Expense) to the D365 Main Account type. If the destination D365 entity uses a different financial dimension framework for cost center or department reporting, we flag this as a required mapping decision before the GL load phase.
Syscom ERP
Multi-currency Configuration
Microsoft Dynamics 365 Business Central
Currency and Exchange Rate Setup
lossySyscom ERP multi-currency setup (currency codes, exchange rate tables, and unrealized gain/loss accounts) maps to D365 Currency and Exchange Rate configuration. We map each source currency to its D365 ISO code equivalent, and the exchange rate table loads into the Exchange Rate Entity in D365. Unrealized currency gain and loss accounts from Syscom map to the Realized and Unrealized Exchange Gain/Loss accounts configured in D365 General Ledger.
Syscom ERP
User / Employee
Microsoft Dynamics 365 Business Central
Worker or User
1:1Syscom ERP user accounts (login credentials, roles, and permissions) map to D365 User records linked to Workers in Human Resources (if the customer licenses HR) or to stand-alone D365 User accounts. We extract role assignments and map them to D365 Security Roles, noting any permission-level gaps where Syscom permissions do not map directly to D365 role-based access. The customer's admin provisions the destination users in Azure Active Directory before migration.
Syscom ERP
Custom Objects / User-Defined Fields
Microsoft Dynamics 365 Business Central
Custom Fields or Extension Objects
1:1Syscom ERP custom objects and user-defined fields (identified during discovery across active modules) map to D365 custom fields (using the Field workspace for Finance and SCM) or extension objects for Business Central. We pre-create the destination custom field schema in a Sandbox environment, validate the data type mapping (text to text, numeric to decimal, date to date), and import the custom field data as a final object load phase after all standard objects are validated.
| Syscom ERP | Microsoft Dynamics 365 Business Central | Compatibility | |
|---|---|---|---|
| Item / Product | Released Product (Product Master)1:1 | Fully supported | |
| Bill of Materials (BOM) | BOM and Formula (Production Bill of Materials)1:1 | Fully supported | |
| Work Order / Manufacturing Order | Production Order1:1 | Fully supported | |
| Customer / Account | Customer1:1 | Fully supported | |
| Vendor / Supplier | Vendor1:1 | Fully supported | |
| Sales Order | Sales Order1:1 | Fully supported | |
| Purchase Order | Purchase Order1:1 | Fully supported | |
| Inventory / Stock | On-hand Inventory (Inventory Dimensions)1:1 | Mapping required | |
| GL Chart of Accounts | General Ledger Account1:1 | Fully supported | |
| Multi-currency Configuration | Currency and Exchange Rate Setuplossy | Fully supported | |
| User / Employee | Worker or User1:1 | Fully supported | |
| Custom Objects / User-Defined Fields | Custom Fields or Extension Objects1:1 | Mapping required |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Syscom ERP gotchas
No documented public API for automated data extraction
Modular architecture requires full module inventory before scoping
On-premise deployments require direct database access coordination
Multi-currency setup must be mapped explicitly at migration time
Microsoft Dynamics 365 Business Central gotchas
Named-user licensing has no concurrent-use relief
API rate limits throttle large-volume migrations
Historical posted transactions require selective migration scoping
NAV-to-Business Central cloud migration requires partner coordination
Custom fields and AL extensions require separate migration handling
Pair-specific challenges
Migration approach
Discovery and extraction method determination
We conduct a structured discovery call to inventory the active Syscom ERP modules, record counts for each object type (Items, BOMs, Customers, Vendors, Sales Orders, POs, Work Orders, Inventory records, GL accounts, Users), and the current deployment type (cloud-hosted or on-premise). For on-premise deployments, we coordinate read-only SQL access with the customer's IT team or agree on a SQL export script to be run by their DBA. For cloud-hosted deployments, we request partner API credentials or application-level export access from Syscom PLC or the customer's Syscom account manager. The discovery output is a written Migration Scope document and an Extraction Plan specifying the method, table references, and data volume estimates per object.
D365 environment provisioning and legal entity setup
The customer provisions a D365 Sandbox (Full Copy for large datasets, Standard for mid-market) and, if needed, a Production environment. We work with the customer's D365 administrator to configure the legal entity, fiscal calendar (with appropriate start date and period structure), accounting currency, and chart of accounts framework in D365 before any data loads. We also configure the inventory dimension groups, site and warehouse structure, customer and vendor groups, and product dimension groups during this phase so that the data schema is ready before extraction begins.
Data extraction, cleansing, and schema mapping
We execute the extraction using the agreed method (SQL export, partner API, or application export) for each object set in dependency order. Items and BOMs extract first (they are referenced by Sales Orders, POs, and Work Orders), followed by Customers and Vendors, then GL accounts, then transactional documents. We cleanse the extracted data for duplicates (using company registration number or email as dedupe keys for accounts), invalid characters, and null-required fields. The mapping document maps each Syscom ERP field to its D365 equivalent by name, type, and dimension group, and flags any fields that require custom field creation before load.
Sandbox migration and reconciliation
We run a full migration into the D365 Sandbox environment using production-like data volume. The customer's IT lead and finance lead perform reconciliation against the source data: record counts per object, GL trial balance comparison, inventory on-hand value match, and spot-checks on 25-50 randomly sampled records. Any mapping corrections, missing dimension assignments, or currency code mismatches are resolved here and documented in the Mapping Change Log. We do not proceed to production migration until the customer signs off on the Sandbox reconciliation report.
Production migration in dependency order
We run production migration in record-dependency order: GL accounts first (chart of accounts is referenced by all transactional modules), then Products and BOMs, then Inventory on-hand (to seed stock before orders), then Customers and Vendors, then Sales Orders and POs (with open/closed status preserved), then Work Orders (linked to BOMs and routes), then Custom Fields and custom object data. Each phase emits a row-count reconciliation report before the next phase begins. We use D365's Data Management framework and Bulk API for large transactional batches with batch chunking and exponential backoff on rate-limit responses.
Cutover, validation, and workflow handoff
We freeze Syscom ERP write access during cutover, run a final delta migration of any records created or modified during the migration window, then hand control to D365 as the system of record. We deliver the Workflow and Automation Inventory document listing every configured workflow, scheduled report, and alert in Syscom ERP with its trigger, conditions, and recommended D365 equivalent (Power Automate flow, Alert framework, or Business Rule). We do not rebuild workflows as D365 workflows inside the migration scope; that is a separate engagement or an internal admin task. We support a one-week hypercare window for reconciliation issues raised by the customer's team.
Platform deep dives
Syscom ERP
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Business Central
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Syscom ERP and Microsoft Dynamics 365 Business Central.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Syscom ERP: Not publicly documented.
Data volume sensitivity
Syscom ERP doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Syscom ERP to Microsoft Dynamics 365 Business Central migration scoping. Not seeing yours? Book a call.
Walk through your Syscom ERP to Microsoft Dynamics 365 Business Central migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Syscom ERP
Other ways to arrive at Microsoft Dynamics 365 Business Central
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.