Tally to Dynamics 365 Business Central Migration: A Guide for Businesses

Tally built its reputation on simplicity and speed. For UAE businesses running a single entity with straightforward accounting, it does that job well.

The problem emerges when the business scales – adding entities, expanding across the GCC, requiring consolidated reporting, or needing to manage UAE Corporate Tax alongside VAT compliance. Tally is an on-premise accounting tool. Business Central is a cloud-native ERP. The gap between the two widens as business complexity grows.

In 2026, migration from Tally to Dynamics 365 Business Central is one of the most common ERP transitions in the UAE market – particularly among SMEs in construction, trading, professional services, and manufacturing that have outgrown what Tally can offer.

Why UAE Businesses Are Moving from Tally to Business Central

Tally’s limitations become visible at predictable points in a business’s growth journey.

Scalability. Tally handles single-entity accounting well. As businesses add subsidiaries, joint ventures, or GCC operations, managing multiple Tally files with manual consolidation becomes unmanageable. Business Central’s multi-entity architecture handles group-level consolidation natively.

Cloud access. Tally is fundamentally an on-premise system. Remote access requires workarounds – VPN, desktop sharing, or Tally’s own remote server setup. Business Central is cloud-hosted by default, accessible from any device with an internet connection, with automatic Microsoft updates and no server maintenance overhead.

UAE compliance depth. Business Central has built-in UAE VAT configuration, FTA e-invoicing support, and Corporate Tax reporting frameworks. As UAE regulatory requirements evolve, Microsoft updates Business Central accordingly – twice per year. Tally users in the UAE have had to rely on third-party add-ons and manual workarounds for FTA compliance.

Reporting and analytics. Tally’s reporting is functional but limited. Business Central integrates natively with Power BI, Excel, and Microsoft Teams – giving finance teams and management real-time visibility into profitability, cash flow, and operational performance without manual report exports.

Integration. Modern UAE businesses need their ERP to connect to their CRM, HR system, e-commerce platform, and procurement tools. Business Central supports REST API and native Microsoft ecosystem integrations. Tally integrations are possible but typically require significant custom development.

With the reasons established, the practical question becomes what the migration actually involves.

What Data Migrates from Tally to Business Central

Understanding what migrates – and what does not – is essential for setting realistic expectations before a Tally to Business Central migration begins.

What typically migrates:

• Chart of accounts and ledger masters. Tally organises accounts through Ledger Groups and individual Ledgers. These map to Business Central’s G/L account structure, but the mapping is not automatic – every ledger must be reviewed, reclassified, and mapped to the correct BC account type and posting group.
• Customer and supplier masters. Contact records, payment terms, credit limits, VAT registration numbers, and bank details all migrate. Data quality in Tally masters varies considerably – duplicate records, missing VAT numbers, and inconsistent naming conventions are common problems encountered during this stage.
• Opening balances. The confirmed account balances as of the go-live cut-off date migrate as opening entries in Business Central. Getting these agreed and signed off by the finance team before go-live is a critical milestone.
• VAT transaction history. Completed VAT periods from Tally are brought across for audit trail and reference. Open transactions that span the go-live date require careful handling to avoid double-counting.
• Inventory masters and opening stock. Item records, units of measure, pricing structures, and stock quantities as at go-live date migrate. Historical inventory movements are typically not migrated – only the opening position.

What typically does not migrate:

Historical transaction detail beyond opening balances is usually not migrated in full. Most businesses agree to bring across the current financial year’s transactions plus one prior year. Earlier history is archived from Tally and made available for reference but not loaded into Business Central.

Tally customisations – .TDL scripts and third-party add-ons – do not transfer. Any functionality they provided needs to be assessed against what Business Central delivers natively, and any genuine gap addressed through configuration or certified extensions from Microsoft AppSource.

Tally reports and print formats also do not carry over. Business Central has its own reporting structure, and most UAE businesses find that the standard reports cover their needs without custom development.

Where specific formats are required – custom invoice layouts, FTA-compliant VAT reports, or management dashboards – these are configured in Business Central as part of the implementation scope.

With a clear picture of what migrates, the next question is how the migration actually runs.

The Tally to Business Central Migration Process

Phase 1: Assessment and Scoping

Before any data is extracted, the migration team must understand your current Tally environment in detail – the number of companies in Tally, the structure of your chart of accounts, the volume and quality of your master data, your integration points, and your regulatory reporting requirements.

This phase produces a Migration Scope Document: an agreed record of exactly what will migrate, what the go-live cut-off date will be, how historical data will be handled, and what success looks like for validation. Attempting migration without this document is the most common cause of scope disputes and delays later.

For businesses with a standard scope, our QuickStart Business Central methodology pre-packages the configuration and migration decisions common to UAE businesses migrating from Tally, reducing assessment time and compressing the overall timeline.

For UAE businesses, assessment also covers the current VAT configuration in Tally, any FTA audit requirements, and Corporate Tax documentation that needs to be accessible post-migration.

With scope agreed and documented, data extraction can begin.

Phase 2: Data Extraction and Mapping

Data extraction from Tally is typically done through Tally’s built-in export functions or third-party migration tools, producing Excel or XML files containing ledger masters, vouchers, outstanding balances, and inventory records.

The mapping stage is where the most careful work happens. Every Tally ledger is reviewed and assigned to the corresponding Business Central G/L account, customer, vendor, or item record. Tax codes are mapped to BC’s VAT posting groups. Currency codes are verified. Bank accounts are matched.

This stage almost always surfaces data quality issues – duplicate customer records, inconsistent ledger naming, missing tax registration numbers, and legacy balances that have never been reconciled. Addressing these before migration rather than after go-live is critical. Data that enters Business Central incorrectly will be significantly harder to fix once the system is live.

With clean, mapped data ready, configuration and testing can begin.

Phase 3: Configuration, Sandbox, and Validation

With mapping complete, the implementation team configures Business Central – setting up the chart of accounts, posting groups, tax configurations, approval workflows, bank connections, and any industry-specific modules required.

Migrated data is loaded into a sandbox environment first. The finance team then validates the output: trial balances must match Tally’s closing position, customer and supplier balances must reconcile, and VAT balances must be consistent.

Standard practice is to run at least two validation cycles before proceeding to the live environment.

Dynamics 365 training for finance and operations users is delivered during this phase – before go-live, not after. Role-based training ensures each user understands the workflows relevant to their function in Business Central, not just a generic system walkthrough.

With validation complete and users trained, the project moves to go-live.

Phase 4: Go-Live and Cutover

Cutover is the final migration of live data – opening balances as at the agreed cut-off date, outstanding customer invoices, outstanding supplier invoices, and confirmed inventory positions – into the production Business Central environment.

A clean cutover requires the Tally books to be closed as of the cut-off date before Business Central goes live.

Running both systems simultaneously for an extended period creates reconciliation complexity and should be minimised. Most UAE migrations run a brief parallel period of one to two weeks for validation, not as an ongoing operating model.

The immediate post-go-live period – hypercare – is where Burhani™ ensures issues are caught and resolved quickly, before they compound. Our Tally to Business Central migration service includes a structured hypercare period as standard.

Understanding the challenges that most commonly arise helps you prepare for them before the project begins.

Common Challenges When Migrating from Tally

Ledger proliferation. Tally makes it easy to create new ledgers, and many businesses accumulate hundreds of rarely-used accounts over years of operation. A Tally-to-BC migration is an opportunity to rationalise the chart of accounts – but this requires decisions from the finance team that take time and sometimes create internal disagreement.

VAT mapping complexity. UAE businesses running Tally often have inconsistent VAT coding across transactions – particularly for goods that attract different VAT rates or exemptions. Mapping these correctly to Business Central’s tax posting groups requires careful review of historical transactions rather than a simple field-to-field transfer.

Opening balance sign-off delays. Getting the finance team and external auditors to sign off confirmed opening balances is consistently the longest administrative bottleneck in UAE Tally migrations.

This often requires reconciling Tally balances against bank statements, supplier confirmations, and customer statements that have not been reviewed in months. Starting this process early – well before the planned go-live date – is the most effective way to prevent timeline overruns.

User adoption. Tally users are accustomed to a keyboard-driven, command-line interface. Business Central’s GUI-based workflow is a significant adjustment. Role-based pre-go-live training and a structured hypercare support period are both essential, not optional, for successful adoption.

All four challenges are manageable with the right preparation and the right partner.

Final Thoughts

A Tally to Business Central migration is not simply a data transfer. It is a structured business change that requires clean data, agreed scope, configured workflows, trained users, and a partner with genuine UAE migration experience.

Done well, the migration delivers a cloud-native ERP that grows with your business – handling multi-entity operations, UAE regulatory compliance, and real-time reporting in a way that Tally was never designed to provide.

Frequently Asked Questions