Dynamics 365 Business Central to SYSPRO Migration

Q: How are Business Central Customer Payments and Vendor Payments handled in SYSPRO?

Neither maps directly: Customer Payments migrate as Cash Book Entries using a receipt-type workaround, and Vendor Payments migrate as Cash Book Entries using a payment-type workaround. Before migration, SYSPRO must have the correct receipt and payment types configured, because the import will fail or land incorrectly if those prerequisite records are absent. Your SYSPRO administrator should set up and confirm those types during the scoping phase, not after data has been loaded.

Q: What happens to my Business Central Tax Areas when they move to SYSPRO?

Tax Areas do not have a direct equivalent in SYSPRO and are mapped to Tax Codes through a workaround, because the two structures differ significantly. Tax Codes must exist in SYSPRO before any tax-bearing transactions (invoices, orders) can import, so your team needs to create and verify those codes first. After migration, you should review every mapped tax code against your original tax area configuration to confirm rates and applicability rules are correct, as this cannot be validated automatically.

Q: Will my Business Central currency and exchange-rate data come across to SYSPRO?

Currency definitions are migrated through a workaround that maps them to SYSPRO Currency Rates, but exchange rates require separate handling and are not carried across as part of the same automated process. If your Business Central environment holds a history of rate changes, those rates need to be reviewed and loaded into SYSPRO independently after the currency definitions land. Failing to address exchange rates before you post historical multi-currency transactions will produce incorrect converted values in SYSPRO.

Q: Do Business Central custom fields and extensions migrate to SYSPRO automatically?

No. Custom fields added to Business Central through AL extensions are not exposed by the standard API v2.0; they require custom API pages built in AL before ClonePartner can read them. On the SYSPRO side, any equivalent data would need to land in custom form fields stored in plus tables (for example ArCustomer+), which must be created in your SYSPRO instance before the migration runs. Both the AL pages and the SYSPRO plus-table definitions are configuration work your team or implementation partner handles; ClonePartner moves the data once those endpoints exist.

Q: Can posted Business Central ledger entries be imported directly into SYSPRO GL history?

No, and there is a constraint on both sides. Business Central's posted GL, customer and vendor ledger entries cannot be edited, but they can be read and extracted. Posted history is usually loaded into SYSPRO as opening balances or reference data, rather than re-posted as live transactions. Your team needs to plan for that posting step in SYSPRO before go-live, and should confirm with your SYSPRO administrator which periods should remain open during the migration window.

Q: What API access and version requirements need to be in place before the migration can start?

On the Business Central side, ClonePartner uses API v2.0 and OData v4; your environment must have API access enabled and ClonePartner's service credential granted the correct permission sets, and Business Central's API rate limits affect throughput on large datasets. On the SYSPRO side, data loads through SYSPRO's business objects, such as ARSSCS (AR Customer Maintenance), so e.net must be licensed and reachable and an operator logon provided. If you run multiple SYSPRO companies or multiple Business Central environments, each requires its own authentication context and must be scoped separately.

CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from Dynamics 365 Business Central 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 Dynamics 365 Business Central 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 Dynamics 365 Business Central 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 Dynamics 365 Business Central 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 Dynamics 365 Business Central 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 Dynamics 365 Business Central to SYSPRO. Can't find what you're looking for? Talk to our team.

Dynamics 365 Business Central → 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

Dynamics 365 Business Central → SYSPRO

6 questions

How are Business Central Customer Payments and Vendor Payments handled in SYSPRO?

Neither maps directly: Customer Payments migrate as Cash Book Entries using a receipt-type workaround, and Vendor Payments migrate as Cash Book Entries using a payment-type workaround. Before migration, SYSPRO must have the correct receipt and payment types configured, because the import will fail or land incorrectly if those prerequisite records are absent. Your SYSPRO administrator should set up and confirm those types during the scoping phase, not after data has been loaded.

What happens to my Business Central Tax Areas when they move to SYSPRO?

Tax Areas do not have a direct equivalent in SYSPRO and are mapped to Tax Codes through a workaround, because the two structures differ significantly. Tax Codes must exist in SYSPRO before any tax-bearing transactions (invoices, orders) can import, so your team needs to create and verify those codes first. After migration, you should review every mapped tax code against your original tax area configuration to confirm rates and applicability rules are correct, as this cannot be validated automatically.

Will my Business Central currency and exchange-rate data come across to SYSPRO?

Currency definitions are migrated through a workaround that maps them to SYSPRO Currency Rates, but exchange rates require separate handling and are not carried across as part of the same automated process. If your Business Central environment holds a history of rate changes, those rates need to be reviewed and loaded into SYSPRO independently after the currency definitions land. Failing to address exchange rates before you post historical multi-currency transactions will produce incorrect converted values in SYSPRO.

Do Business Central custom fields and extensions migrate to SYSPRO automatically?

No. Custom fields added to Business Central through AL extensions are not exposed by the standard API v2.0; they require custom API pages built in AL before ClonePartner can read them. On the SYSPRO side, any equivalent data would need to land in custom form fields stored in plus tables (for example ArCustomer+), which must be created in your SYSPRO instance before the migration runs. Both the AL pages and the SYSPRO plus-table definitions are configuration work your team or implementation partner handles; ClonePartner moves the data once those endpoints exist.

Can posted Business Central ledger entries be imported directly into SYSPRO GL history?

No, and there is a constraint on both sides. Business Central's posted GL, customer and vendor ledger entries cannot be edited, but they can be read and extracted. Posted history is usually loaded into SYSPRO as opening balances or reference data, rather than re-posted as live transactions. Your team needs to plan for that posting step in SYSPRO before go-live, and should confirm with your SYSPRO administrator which periods should remain open during the migration window.

What API access and version requirements need to be in place before the migration can start?

On the Business Central side, ClonePartner uses API v2.0 and OData v4; your environment must have API access enabled and ClonePartner's service credential granted the correct permission sets, and Business Central's API rate limits affect throughput on large datasets. On the SYSPRO side, data loads through SYSPRO's business objects, such as ARSSCS (AR Customer Maintenance), so e.net must be licensed and reachable and an operator logon provided. If you run multiple SYSPRO companies or multiple Business Central environments, each requires its own authentication context and must be scoped separately.

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 Dynamics 365 Business Central.

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 Dynamics 365 Business Central 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 Dynamics 365 Business Central during the migration?

No. Dynamics 365 Business Central 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 Dynamics 365 Business Central to SYSPRO?

Very little. The bulk load runs in the days before go-live while Dynamics 365 Business Central stays live. We go live on a Monday, never a Friday: Dynamics 365 Business Central 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 Dynamics 365 Business Central 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 Dynamics 365 Business Central to SYSPRO with precision & ease

Intelligent Human-Verified Data Mapping

Real migration stories

Fully customizable engineer-led migration

Your timeline. Our engineers.

Your Dynamics 365 Business Central to SYSPRO migration, step by step

Pros and cons of different migration options