ERP migration

Migrate from Syscom ERP to Microsoft Dynamics 365 Business Central

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 logo

Syscom ERP

Source

Microsoft Dynamics 365 Business Central

Destination

Microsoft Dynamics 365 Business Central logo

Compatibility

92%

11 of 12

objects map 1:1 between Syscom ERP and Microsoft Dynamics 365 Business Central.

Complexity

BStandard

Timeline

6-10 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Syscom ERP logo

Syscom ERP

What's pushing teams away

  • Concentrated UK presence — international or multi-country expansion is harder to support than with global vendors like SAP Business One, NetSuite or Dynamics 365 Business Central.
  • Public pricing is not surfaced — buyers must engage Syscom sales to learn per-user and per-module costs, complicating budget comparisons.
  • Public API documentation and developer portal are not surfaced — integrations with non-Syscom systems typically rely on partner-led implementation.
  • Modest press footprint and limited independent review volume (Crozdesk score 55/100) make peer benchmarking harder than for category leaders.
  • Customers outgrowing mid-market complexity may face heavy implementation work to scale into multi-entity consolidation or multi-currency operations that bigger ERPs handle natively.

Choosing

Microsoft Dynamics 365 Business Central logo

Microsoft Dynamics 365 Business Central

What's pulling them in

  • Deep integration with Microsoft 365, Power BI, and Power Platform means organizations already on the Microsoft stack get identity, reporting, and workflow continuity out of the box.
  • Unified financials, sales, service, and operations replace multiple disconnected systems — users report that data entered once flows through purchase orders, invoicing, and approvals without manual re-entry.
  • Copilot AI features (predictive analytics, embedded business intelligence) are included in both Essentials and Premium tiers, addressing demand for AI without separate module purchases.
  • Named-user licensing with no concurrent model appeals to organizations that want predictable per-seat costs even if some users access the system infrequently.
  • Strong partner ecosystem with certified NAV-to-Business Central migration specialists gives mid-market companies confidence the cutover from legacy Navision can be executed reliably.

Object mapping

How Syscom ERP objects map to Microsoft Dynamics 365 Business Central

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

maps to

Microsoft Dynamics 365 Business Central

Released Product (Product Master)

1:1
Fully supported

Syscom 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)

maps to

Microsoft Dynamics 365 Business Central

BOM and Formula (Production Bill of Materials)

1:1
Fully supported

Syscom 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

maps to

Microsoft Dynamics 365 Business Central

Production Order

1:1
Fully supported

Syscom 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

maps to

Microsoft Dynamics 365 Business Central

Customer

1:1
Fully supported

Syscom 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

maps to

Microsoft Dynamics 365 Business Central

Vendor

1:1
Fully supported

Syscom 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

maps to

Microsoft Dynamics 365 Business Central

Sales Order

1:1
Fully supported

Syscom 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

maps to

Microsoft Dynamics 365 Business Central

Purchase Order

1:1
Fully supported

Syscom 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

maps to

Microsoft Dynamics 365 Business Central

On-hand Inventory (Inventory Dimensions)

1:1
Mapping required

Current 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

maps to

Microsoft Dynamics 365 Business Central

General Ledger Account

1:1
Fully supported

Syscom 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

maps to

Microsoft Dynamics 365 Business Central

Currency and Exchange Rate Setup

lossy
Fully supported

Syscom 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

maps to

Microsoft Dynamics 365 Business Central

Worker or User

1:1
Fully supported

Syscom 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

maps to

Microsoft Dynamics 365 Business Central

Custom Fields or Extension Objects

1:1
Mapping required

Syscom 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.

Gotchas + challenges

What specifically takes care here

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 logo

Syscom ERP gotchas

High

No documented public API for automated data extraction

Medium

Modular architecture requires full module inventory before scoping

Medium

On-premise deployments require direct database access coordination

Low

Multi-currency setup must be mapped explicitly at migration time

Microsoft Dynamics 365 Business Central logo

Microsoft Dynamics 365 Business Central gotchas

High

Named-user licensing has no concurrent-use relief

High

API rate limits throttle large-volume migrations

Medium

Historical posted transactions require selective migration scoping

Medium

NAV-to-Business Central cloud migration requires partner coordination

Low

Custom fields and AL extensions require separate migration handling

Pair-specific challenges

  • Syscom ERP has no public API; extraction requires partner access or direct database export

    Syscom ERP does not publish a public REST or SOAP API in our research. For cloud-hosted deployments, we coordinate with the customer's Syscom account manager or implementation partner to obtain partner API access credentials or a data export via the application's built-in export functions. For on-premise deployments, we work with the customer's IT team to run SQL SELECT exports from the SQL Server backend, either via a read-only database user we provision or a SQL export script executed by the customer's DBA. This extraction method adds one to three weeks to the discovery phase compared to API-based migrations and requires the customer's IT team to be actively involved in data extraction.

  • Syscom modular architecture means full module inventory is required before scoping

    Syscom ERP8 is sold as a modular system where no two customers have the same active module set. Before we can scope the migration accurately, we must inventory which modules are live at the source: Financials, Distribution, Manufacturing, CRM, and any vertical add-ons like ApparelX. Missing a module during discovery means the corresponding object set is left behind. We include a Syscom module checklist in every discovery call and cross-reference the customer's license agreement or implementation contract to confirm module scope. BOM and Work Order migration only applies if the Manufacturing module is active.

  • D365 requires legal entity and fiscal calendar setup before GL migration

    Microsoft Dynamics 365 Finance requires a legal entity to be configured before any GL accounts, customers, vendors, or products can be loaded. The customer's Syscom ERP data may span a single company or multiple entities, and D365 requires each entity to have a defined fiscal calendar, accounting currency, and address. We flag this as a pre-migration decision point. If the customer uses multiple Syscom companies for different divisions, each maps to a separate D365 legal entity with intercompany accounting configured separately. This setup typically adds one to two weeks to the project timeline before data migration begins.

  • BOM explosion requires recursive extraction and version resolution

    Multi-level BOMs in Syscom ERP must be extracted as a full recursive tree to preserve parent-component relationships in D365. We use a recursive SQL query against the Syscom BOM tables to extract all levels, then construct D365 BOM and Formula records with version links. Alternative BOMs and BOMs marked as inactive in Syscom are loaded as inactive versions in D365. If the customer's Syscom ERP uses BOMs with phantom assembly structures or co-products, these map to D365 Formula with appropriate by-product handling. BOM migration without full recursion results in incomplete production orders.

  • On-premise extraction requires DBA coordination and read-only database access

    For on-premise Syscom ERP customers, database extraction requires coordination with the customer's IT team to grant read-only access to the SQL Server or database backend hosting Syscom ERP. We need either a SQL login with db_datareader permissions or a DBA to run our export scripts. Cloud-hosted customers bypass this step by providing application-level credentials or partner portal access. We document the extraction method in the Data Migration Plan and include a one-week buffer for IT team scheduling. If the customer's IT team is unavailable for database access within the project window, the timeline extends accordingly.

Migration approach

Six steps for a successful Syscom ERP to Microsoft Dynamics 365 Business Central data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Syscom ERP logo

Syscom ERP

Source

Strengths

  • Modular architecture lets manufacturers and distributors pay only for modules they use, reducing total cost.
  • Multi-currency support accommodates international trade and multi-entity operations without a separate currency add-on.
  • On-premise and cloud deployment options give customers flexibility on data residency and infrastructure control.
  • 40+ years of Syscom PLC market presence indicates stability and long-term support commitment.
  • Industry-specific variants like ApparelX indicate vertical depth for apparel-sector customers.

Weaknesses

  • No publicly documented API or developer portal found in our research, limiting automated migration tooling access.
  • Modular pricing model means total cost is opaque until a full module inventory is completed.
  • No public review dataset found on G2, Capterra, or TrustRadius, making independent quality assessment difficult.
  • Smaller company size ($8.5M revenue) relative to major ERP vendors raises questions about long-term R&D investment and support capacity.
  • No published SLA or uptime guarantees found, which is a concern for cloud-deployed customers.
Microsoft Dynamics 365 Business Central logo

Microsoft Dynamics 365 Business Central

Destination

Strengths

  • Tight integration with Microsoft 365 (Outlook, Teams, SharePoint) for users already in the Microsoft ecosystem.
  • Includes Copilot AI, predictive analytics, and embedded Power BI dashboards at no additional cost in both license tiers.
  • Supports multiple companies within a single tenant for holding-company or multi-entity organizational structures.
  • Open REST API v2.0 with OAuth 2.0 authentication and data entity abstraction layer for developer-friendly integrations.
  • Strong partner ecosystem specializing in NAV-to-Business Central migrations provides implementation confidence for legacy upgrades.

Weaknesses

  • Named-user licensing model means every active user account requires a paid license — no concurrent access model to reduce costs for occasional users.
  • SaaS-only deployment means no on-premises option; organizations requiring full data residency control may not have viable alternatives within Microsoft's stack.
  • Manufacturing module (Production Orders, routing, work centers) is only available on Premium tier, pushing cost-sensitive manufacturers to higher-priced plans.
  • Customization and extension development requires AL language knowledge and developer licenses, limiting what power users can do without a partner engagement.
  • Global pricing increases effective October 2024 and again October 2025 after five years of stable pricing, creating budget uncertainty for existing customers.

Complexity grading

How hard is this migration?

Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

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

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Syscom ERP: Not publicly documented.

  • Data volume sensitivity

    B

    Syscom ERP doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Syscom ERP to Microsoft Dynamics 365 Business Central migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Syscom ERP to Microsoft Dynamics 365 Business Central data migrations

Answers to the questions buyers ask most during Syscom ERP to Microsoft Dynamics 365 Business Central migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Migrations using SQL export from on-premise Syscom ERP with under 100,000 total records and no complex BOM hierarchies land in six to ten weeks. Migrations from cloud-hosted Syscom ERP with partner API extraction, multi-level BOMs, Work Order routing, multi-warehouse inventory, and historical transactional data move to fourteen to twenty-four weeks because of extraction coordination, BOM explosion processing, and inventory valuation reconciliation. The D365 configuration phase (legal entity, chart of accounts, dimension groups) adds one to two weeks before data migration begins and is scoped separately from the extraction timeline.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Syscom ERP.
Land in Microsoft Dynamics 365 Business Central, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day