Microsoft Dynamics NAV to SYSPRO Migration

Q: How do NAV VAT Posting Groups migrate to SYSPRO tax codes?

NAV's VAT posting group system uses a matrix of business and product posting groups to derive rates, which has no direct equivalent in SYSPRO. During migration, each effective VAT rate combination is flattened into a single SYSPRO Tax Code record. Any posting group logic that calculates rates conditionally — for example, reverse-charge or intra-EU rules — cannot be reproduced by the data migration alone and will need to be reconfigured manually in SYSPRO's tax setup after the data lands.

Q: What happens to NAV Sales Credit Memos when they move to SYSPRO?

SYSPRO's AR module does not have a standalone credit memo entity that maps one-for-one from NAV, so credit memos are imported as negative AR invoices. The document type changes, but the amounts, customer, and line detail are preserved. You should verify that your SYSPRO AR aging and statement reports treat negative invoices the same way your team previously used credit memos, since reporting presentation may differ.

Q: Can historical NAV General Ledger Entries be migrated, or only the Chart of Accounts?

NAV's posted GL entries are read-only and cannot be written back via API, so they cannot be migrated as individual ledger entries. Instead, historical GL balances are brought across as GL Journal Entries in SYSPRO using opening-balance journals, which means the transaction-level audit trail from NAV is not replicated line-by-line in SYSPRO. If you need queryable transaction history, plan to keep a read-only NAV instance or export the detail to a reporting database separately — that archiving work is outside the scope of the data migration ClonePartner performs.

Q: Does my NAV version affect what data can actually be extracted?

NAV versions before 2018 (NAV 2017, NAV 2016, and earlier) do not expose REST APIs, so extraction relies on SOAP or OData web services, or XMLport-based data exchange. Standard REST API endpoints used in newer versions — and in Business Central — are unavailable on classic NAV, which means any custom fields added via table modifications on those older versions are also unlikely to be surfaced without custom OData pages being created first. Before scoping your migration, confirm which NAV version and service pack you are running so the correct extraction method can be planned.

Q: How are NAV Contacts migrated when they include both customer and supplier contacts?

SYSPRO's standard contact entity maps to Customer Contacts, so a direct transfer of all NAV Contacts in a single pass is not possible. NAV contact records linked to vendors must be identified and split out before import; those vendor-linked contacts have no native home in the standard SYSPRO supplier record and will require a manual review to determine whether they should be stored in custom form fields in the [ArCustomer+] or equivalent plus tables, or handled another way. This split should be agreed during scoping, as skipping it risks vendor contact data being silently dropped or misrouted.

Q: What prerequisite records must exist in SYSPRO before the migration data can be loaded?

Several SYSPRO business objects enforce referential integrity at import time, meaning dependent records will reject if their prerequisites are absent. Specifically, GL account codes (migrated from the NAV Chart of Accounts), warehouse codes, and Tax Codes derived from NAV VAT posting groups must all be present before Inventory items, AR/AP invoices, or journal entries can be posted successfully. ClonePartner stages the migration in dependency order — GL accounts and tax codes first, then master data, then transactional documents — but any GL accounts or tax codes that are net-new to SYSPRO and were not in NAV will need to be created manually in SYSPRO before the relevant transaction records are loaded.

CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from Microsoft Dynamics NAV to SYSPRO exactly to your needs with our flexible customization options. Our experts will configure the perfect migration plan for your business.

Migration Filters

Data Types

MIGRATION TIMELINE

Your Microsoft Dynamics NAV to SYSPRO migration, step by step

See how long your migration will take from start to finish. Drag the slider to estimate based on your data volume.

How many records are you migrating?

<10K 50K 100K 250K 500K 1M 2M 5M 10M+

Checklist ~3 days

Sample 1 day

Review ~2 days

Full 2 days

Delta 1 day

Your team ClonePartner

Estimated total

~9 business days

Migration Checklist

1 day · ClonePartner ~2 days · Your team

We prepare the optimal data mapping as a shareable spreadsheet. Your team reviews, approves, and adds any customizations.

Sample Migration

1 day · ClonePartner

We run a test migration with a representative sample of your data to verify mapping accuracy and identify any potential issues before the full run.

Review & Approve

~2 days · Your team

Your team reviews the sample migration results, confirms data accuracy and mapping, and gives the go-ahead for the full migration.

Full Migration

2 days · ClonePartner

We execute the complete migration of all your data to your new SYSPRO, with real-time progress tracking and comprehensive logging.

Delta Migration

1 day · ClonePartner

We capture and transfer any new data that was added or updated during the main migration to ensure no data is lost. This final sync keeps everything current.

Feature / Criteria	ClonePartner	Automated Tools	CSV Import	In-house migration
Custom Scripting for complex data	✓ Engineers build & maintain	✗ No	⚠ Manual	✓ Yes – but costly
Sandbox & Pilot Migrations	✓ Full sandbox + pilot plans	⚠ Limited	✗ No	⚠ Often Informal
Manual validation & reconciliation	✓ Automated + manual QA	✗ No	✓ Yes (Manual)	✓ Heavy manual effort
Backup & rollback plan	✓ Robust procedures	✗ No	✗ No	⚠ Often incomplete
Handles automation and integrations	✓ Full support	⚠ Partial	✗ No	⚠ Possible but fragmented
Post-migration engineer support	✓ Dedicated engineers	✗ No	✗ No	⚠ Limited close support
Adaptable to API changes	✓ Proactive adaptation	✗ No	⚠ Manual fixes	⚠ Slower response
Turnaround / close predictability	✓ Predictable close timelines	⚠ Fast but brittle	⚠ Slow and manual	⚠ Often slower
Data Security & Compliance	✓ High – enterprise grade	⚠ Medium (depends)	⚠ Low (manual)	⚠ Hidden gaps common
Pricing predictability	✓ Transparent & fixed	⚠ Low (per-job)	⚠ Low (manual hours)	⚠ High/variable OPEX
End-to-end project management	✓ Full E2E delivery & PM	✗ No	✗ No	⚠ Often partial
Business impact & opportunity cost	✓ No diversion of staff	✗ No	✗ No	⚠ Diverts engineering

What does an Engineer-led migration mean anyway?

Speed & Accuracy: Our Blended Method

We blend automation (smart scripts, bulk APIs) with human expertise for speed without risk. Our engineers manually check every mapping, validation, and exception.

You get:

Speed of automation for bulk record migration
Precision of engineers verifying integrity and business logic
Pilot migrations and sandbox testing to catch issues early
Real-time validation reports and rollback readiness

Result: 50x faster migrations than manual imports — with near-zero error rates.

Handling the Tricky Tech and API Details

The Microsoft Dynamics NAV and SYSPRO APIs each behave differently, which is where our engineers shine. We build custom logic to handle the data quirks where generic tools typically break.

We handcraft API logic for:

Field mapping and transformation
Pagination, rate-limit handling, and throttling
Preserving GL history, journal entries, and transaction records
Syncing custom fields, modules, and chart of accounts without breaking structure

Our scripts: Natively retry failed calls, re-queue large attachments, and ensure data parity.

No Guesswork

We don't just promise smooth migrations—we measure and prove them. Every client receives a Migration Validation Report with all metrics.

Typical results across projects:

100% record-count parity between your Microsoft Dynamics NAV data and SYSPRO
Zero downtime during staged cutovers
99.9% attachment integrity (verified via checksum)
Full automation and preservation of all business rules

Our standard: Includes full audit-trail and reconciliation preservation and 30 days of engineer-assigned support post go-live.

We Adapt to Your Setup (Not the Other Way Around)

No two teams configure Microsoft Dynamics NAV or SYSPRO exactly the same way—with unique modules and data. We customize every migration script to fit your exact workflow, modules, and chart of accounts.

Our engineers adapt for:

Custom fields, modules, and workflows
Multi-entity or multi-company setups
Historical imports and partial (date-based) migrations
Integration re-mapping for banking, payroll, or reporting tools

The promise: If your data doesn't fit a standard template, we build one just for you.

FAQ

Frequently Asked Questions

Everything you need to know about migrating from Microsoft Dynamics NAV to SYSPRO. Can't find what you're looking for? Talk to our team.

Microsoft Dynamics NAV → SYSPRO 6 Before you start 2 Data & mapping 2 Timeline & downtime 3 Security & access 1 Pricing 1 After go-live 5

Still have questions?

Book a free 30-minute consultation with our team.

Contact our team

Microsoft Dynamics NAV → SYSPRO

6 questions

How do NAV VAT Posting Groups migrate to SYSPRO tax codes?

NAV's VAT posting group system uses a matrix of business and product posting groups to derive rates, which has no direct equivalent in SYSPRO. During migration, each effective VAT rate combination is flattened into a single SYSPRO Tax Code record. Any posting group logic that calculates rates conditionally — for example, reverse-charge or intra-EU rules — cannot be reproduced by the data migration alone and will need to be reconfigured manually in SYSPRO's tax setup after the data lands.

What happens to NAV Sales Credit Memos when they move to SYSPRO?

SYSPRO's AR module does not have a standalone credit memo entity that maps one-for-one from NAV, so credit memos are imported as negative AR invoices. The document type changes, but the amounts, customer, and line detail are preserved. You should verify that your SYSPRO AR aging and statement reports treat negative invoices the same way your team previously used credit memos, since reporting presentation may differ.

Can historical NAV General Ledger Entries be migrated, or only the Chart of Accounts?

NAV's posted GL entries are read-only and cannot be written back via API, so they cannot be migrated as individual ledger entries. Instead, historical GL balances are brought across as GL Journal Entries in SYSPRO using opening-balance journals, which means the transaction-level audit trail from NAV is not replicated line-by-line in SYSPRO. If you need queryable transaction history, plan to keep a read-only NAV instance or export the detail to a reporting database separately — that archiving work is outside the scope of the data migration ClonePartner performs.

Does my NAV version affect what data can actually be extracted?

NAV versions before 2018 (NAV 2017, NAV 2016, and earlier) do not expose REST APIs, so extraction relies on SOAP or OData web services, or XMLport-based data exchange. Standard REST API endpoints used in newer versions — and in Business Central — are unavailable on classic NAV, which means any custom fields added via table modifications on those older versions are also unlikely to be surfaced without custom OData pages being created first. Before scoping your migration, confirm which NAV version and service pack you are running so the correct extraction method can be planned.

How are NAV Contacts migrated when they include both customer and supplier contacts?

SYSPRO's standard contact entity maps to Customer Contacts, so a direct transfer of all NAV Contacts in a single pass is not possible. NAV contact records linked to vendors must be identified and split out before import; those vendor-linked contacts have no native home in the standard SYSPRO supplier record and will require a manual review to determine whether they should be stored in custom form fields in the [ArCustomer+] or equivalent plus tables, or handled another way. This split should be agreed during scoping, as skipping it risks vendor contact data being silently dropped or misrouted.

What prerequisite records must exist in SYSPRO before the migration data can be loaded?

Several SYSPRO business objects enforce referential integrity at import time, meaning dependent records will reject if their prerequisites are absent. Specifically, GL account codes (migrated from the NAV Chart of Accounts), warehouse codes, and Tax Codes derived from NAV VAT posting groups must all be present before Inventory items, AR/AP invoices, or journal entries can be posted successfully. ClonePartner stages the migration in dependency order — GL accounts and tax codes first, then master data, then transactional documents — but any GL accounts or tax codes that are net-new to SYSPRO and were not in NAV will need to be created manually in SYSPRO before the relevant transaction records are loaded.

Before you start

2 questions

Do I need professional help for this migration?

While simple migrations can sometimes be handled in-house, professional help ensures zero data loss, proper field mapping, and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.

Does ClonePartner provide guidance before committing?

Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.

Data & mapping

2 questions

Will original document numbers, created dates and user references be preserved?

Yes — we carry them across. Where SYSPRO cannot store one of them natively, it is kept in a custom field or reference on the migrated record, so every record can be traced back to Microsoft Dynamics NAV.

If the new system can't natively support an old record type, what are my options?

We handle it case by case: map it to the closest native object, create a custom field or object, fold it into the parent record as text or an internal note, attach it as a file, or keep it in a read-only archive. You see how your chosen approach looks in a sample migration before we run the full set.

Timeline & downtime

3 questions

How long does the Microsoft Dynamics NAV to SYSPRO migration take?

Most migrations complete within 1–5 business days, depending on data volume and complexity. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.

Will my team lose access to Microsoft Dynamics NAV during the migration?

No. Microsoft Dynamics NAV stays fully operational while we run the bulk load in the background. The only pause is a short freeze before go-live, so the final delta of changed records can be applied and reconciled.

Will there be downtime when migrating from Microsoft Dynamics NAV to SYSPRO?

Very little. The bulk load runs in the days before go-live while Microsoft Dynamics NAV stays live. We go live on a Monday, never a Friday: Microsoft Dynamics NAV freezes before the working day starts, and the final delta covers changed records only, which typically takes about 30 minutes.

Security & access

1 question

Can we whitelist a single IP instead of opening our network to your migration tool?

Yes — all migration traffic runs through a centralized system using one fixed IP, which your IT team can whitelist instead of opening broader network access.

Pricing

1 question

Is migration pricing a flat fee, or does it scale with data volume?

It's a flat fee based on the scope estimate you give us — small variances in actual volume (a bit more or less) don't change the price.

After go-live

5 questions

How do I validate that everything migrated correctly?

Every client receives a Migration Validation Report with comprehensive metrics including record-count parity, attachment integrity verification via checksum, and full audit logs. We also offer unlimited sample migrations so you can verify before committing.

What support do you provide after the migration goes live?

At ClonePartner, we consider ourselves your partners in this journey. We take full accountability for your migration's success. Once your migration goes live, we provide 30 days of comprehensive post-migration support. During this period, we will assist with everything needed to ensure your transition is a complete success.

Will we get a migration report and a mapping sheet linking old record IDs to new ones?

Yes. We provide a comprehensive migration report along with an ID-mapping sheet that links each Microsoft Dynamics NAV record — customers, suppliers, items, orders and invoices — to its new ID in SYSPRO. This ensures full traceability and simplifies post-migration verification.

After migration, do I contact ClonePartner or the platform's own support if something looks wrong?

ClonePartner is the contact for anything about the migrated data itself. Platform-level behavior — posting setup, approval workflows, and similar configuration — is handled by SYSPRO's own support or your implementation partner.

Will we get a report showing exactly what migrated versus what didn't?

Yes. You get a final reconciliation report comparing source and target counts for every object.

Migrate from Microsoft Dynamics NAV to SYSPRO with precision & ease

Intelligent Human-Verified Data Mapping

Real migration stories

Fully customizable engineer-led migration

Your timeline. Our engineers.

Your Microsoft Dynamics NAV to SYSPRO migration, step by step

Top SYSPRO Alternatives 2026: Features, TCO & Migration Paths

Pros and cons of different migration options