Book a Meeting
Contact us
Book a Meeting
Contact us
Contact Us
AccSoft

BUSINESS CENTRAL

Migrating from Legacy ERP to Business Central: Lessons Learned
06
Apr

Migrating from Legacy ERP to Business Central: Lessons Learned 

Migrating from a system is not just about the system; it is about transforming the way your company works. If you are about to embark on the journey to the cloud, here are the hard-earned lessons we learned along the way.  1. “Lift and Shift” is a Trap  The biggest mistake companies make is treating the migration as a copy-and-paste operation. They want to take their messy, convoluted processes from the old system and copy them over to Business Central.  The Lesson: Don’t automate a bad process.  Legacy systems are often messy because the software couldn’t do what the business needed. It required workarounds. Business Central is a much more capable system. Take advantage of the migration to think about your processes. If your old system required five steps to approve a purchase order, see if Business Central can’t do it in two. If you try to make Business Central look and act exactly like your old Legacy system, you will be throwing money away.  2. Data Hygiene is Non-Negotiable  Business thought they had clean data. They didn’t. On extracting data from the old system, we usually discover that there were thousands of obsolete customer data, duplicated vendor data, and inventory items that were not sold in the last ten years.   The Lesson: Don’t boil the ocean.   Don’t migrate everything. You’re moving into a new house. Don’t bring the trash with you.   Archive the old data. Keep the old system accessible. Make it read-only.   Cleanse the master data. Customers. Vendors. Items (GL accounts).   Bring the opening balances. Do bring relevant historical data but not ten years of closed transactional history.  3. Configuration vs. Customization  This is the Golden Rule of Business Central. In the old days, we used to customize the code for everything. We wanted the button to be blue, not grey. We wanted the report to be printed in a specific font.  The Lesson: Stay Standard (Standard = Good).  Every time we customize the code in BC, we make it harder and costlier for future upgrades.  Try and configure the system using standard settings.  Try and look for App Source extensions/add-ons rather than customizing code.  Customize only if it gives you a competitive advantage.  4. The “Excel Trap” is Real  One of the most powerful features of Business Central is its native Excel support. However, be warned that it is also one of the most insidious “features.”  During the go-live of our project, we had users who were afraid of the new UI. Instead of learning how to enter a sales order in BC, they were trying to download everything into Excel, manipulate it there, and paste it back into the system.   The Lesson: Train Early and Train Often  Change management is harder than the technical implementation. People need to be convinced that Business Central is easier than their spreadsheet hell. Invest in “Champion Training” find super users in every department who will be able to pressure their co-workers into using the system correctly.  5. Your Partner Matters More Than the Software  Business Central is a wonderful product, and it’s a platform. It needs a partner to implement it. Chose a partner based on a bid price, and it was a disaster waiting to happen. Chose the lowest bidder, and they treat like a number.   The Lesson: Find a partner that understands your industry, not just the software.  A retail implementation versus a manufacturing implementation is vastly different. Changing partners halfway through the project to one that specialized in the industry costs you more.  6. The Go-Live is Not the Finish Line  Go Live day is, crossing the starting line at a marathon.  The First Month Was a Bumpy Ride  Users forgot passwords. Reports looked a little different. Changes needed to posting groups etc.  The Lesson  Plan for a “Hypercare” period. For the first 4 to 6 weeks after Go Live, be prepared to need extra support. Keep your implementation partner on speed dial. Don’t consider your project complete until you have successfully closed a month-end and run your payroll.  The Bottom Line  Migrating from a legacy ERP system to Business Central is hard. It takes money, time, and a thick skin.  But is it worth it? Yes.  You will have a real-time visibility into business. Can close financials in days instead of weeks. Remote workers can access data from anywhere and you don’t have to think about server maintenance anymore.  If you are considering making the move from a legacy ERP system to Business Central, take the leap, clean your data, and trust the process for your journey to the cloud.
Continue Reading
Agentic ERP: The Next Evolution of Business Central Automation
30
Mar

Agentic ERP: The Next Evolution of Business Central Automation 

For decades, we have been promised “a single source of truth” with ERP (Enterprise Resource Planning). We have gone from messy spreadsheets to neat and ordered databases. And then there has been the revolution of “digital transformation,” which has brought us “cloud connectivity” and “cloud workflows.” But we are now on the cusp of another revolution, another paradigm shift. We are moving from “Digital” to “Autonomous.” And this is where we find ourselves in this new world of Agentic ERP.  For users of Microsoft Dynamics 365 Business Central, this is not just an update to their software; it is a revolution in thinking about how we do business. It is a revolution from standard automation to intelligent agency.  What is Agentic ERP and why does it matter to Business Central users?  From “If-Then” to “Intent-Action”  To understand Agentic ERP, we must understand what comes before it.  Traditional Automation: This is “If-Then” logic. If we have a purchase order, then we send an approval email. The problem is this is very rigid. If things change and we didn’t program it, then it doesn’t work.  Agentic Automation (AI Agents): This is “Intent-Action.” We give it an intent, and it figures out the action to get it there, changing and adapting in real-time.  For example, with Business Central, an AI Agent is not just sending us an alert saying we have low inventory; it is negotiating with the vendor, looking at the budget, and sending us a purchase order and scheduling it, allowing us to do more strategic things.  The Building Blocks: Business Central Meets Co-pilot  We have been building towards this for years. With the addition of Copilot into Business Central, we first got a glimpse of how AI can help with mundane tasks such as writing product descriptions or analysing bank reconciliation data.  But with Agentic ERP, we’re taking Co-pilot to the next level. Instead of it being simply a chatbot sitting next to your data, Agentic AI is a participant in your business. It uses the power of Large Language Models (LLMs) and the data within Business Central to reason, plan, and execute.  What Does Agentic ERP Look Like in Practice?  Let’s consider a typical finance department. Currently, it takes a collections manager hours to look at overdue invoices, determine who to send an email to, and write that email.  In an Agentic Business Central, it would look like this:  Observation: The Agent observes that Customer X is overdue by 15 days.  Reasoning: It reasons that Customer X is overdue and checks its history to see that it is always paid within 45 days but is currently at 30 days. It also knows that it is a high-value customer.  Decision: Instead of sending another “dunning letter” to Customer X, it decides that it would be better to send a nice, personal email.  Action: It sends that email to Customer X through its Outlook program and logs it in Business Central. It then schedules another action for its manager if it doesn’t hear back in 3 days.  The Agent did not just perform its routine; it used its judgment.  The Three Pillars of Agentic ERP  1. Proactivity, Not Reactivity  Traditional ERPs are reactive lumps of data until a human touches them. An Agentic ERP is proactive. An Agentic ERP would forecast cash flow gaps based on market trends and upcoming liabilities and recommend cost-cutting measures before the cash flow gap occurs.  2. Cross-Domain Orchestration  Most business problems are not limited to a single module or function. For instance, a shipping delay in a Supply Chain module would impact a sales promise in a Sales module, which would impact a revenue forecast in a Finance module. An Agentic AI can cross these domains. An Agentic AI would autonomously adjust sales quotes based on supply chain constraints in real-time without a human having to manually update three different screens.  3. Continuous Learning  The more you use Microsoft Dynamics 365 Business Central, the smarter our Agent gets. It learns about you, your business logic, and your vendor relations. Over time, the “noise” of irrelevant alerts decreases, and the “signal” of relevant ones increases.  The Human Role: From Operator to Orchestrator  The biggest fear of AI is replacement of jobs. In the world of Agentic ERP, it’s elevation of jobs instead.  With Business Central taking care of low-level execution tasks like data entry, low-level reconciliation, and basic correspondence, humans get to do the interesting stuff: handling exceptions and thinking strategically. Your finance team goes from being “data entry clerks” to “financial architects.” Your supply chain team goes from chasing purchase orders to designing global supply chains.  Are You Ready?  Agentic ERP is not science fiction; it is being built with Microsoft stack technology today. However, to use it, your Business Central instance must be ready.  Data Quality is King: An Agent is only as smart as the data it is reading. Clean data in Business Central is no longer a “nice to have” but is now a “need to have” to compete.  Process Standardization: Before you let an Agent perform a process, that process needs to be well defined in Business Central.  A Culture of Trust: “I need to approve everything” is not the same as “I trust the system to do it.” It is a cultural change as much as it is a technological change.  The Bottom Line  We’re not going from using software to writing software; we’re going from using software to working with software. For Business Central users, Agentic ERP is the next step in efficiency: not only is your ERP system holding all your business rules, but it is executing them for you. 
Continue Reading
From NAV to Business Central Migration: What Businesses Should Expect
16
Mar

From NAV to Business Central Migration: What Businesses Should Expect 

For years, Microsoft Dynamics NAV has been the workhorse ERP solution for thousands of businesses around the world. It is reliable, robust, and has become an integral part of many business operations. But as technology continues to advance into a cloud-first world, the days of the on-premises legacy server are numbered. Enter Microsoft Dynamics 365 Business Central. It is the successor to NAV, but Migrating from NAV to Business Central is more than that it is a complete overhaul of your business operations.  If you are a NAV user considering making the jump to Business Central, you are likely asking yourself what it means to migrate from NAV to Business Central. Will it hurt? Will I lose all my customizations? How long will it take?  What to Expect  What can businesses expect when making the jump from NAV to Business Central?  1. It’s Not Just an “Upgrade”; It’s a Platform Shift  The largest mental shift for you will be in understanding that this is not just installing Service Pack 2 on your existing server. This is a move from a strictly on-premises solution to a Cloud-first solution, a true SaaS (Software as a Service) model.  What to expect: You will no longer be responsible for managing Windows updates, SQL backups, and server hardware.   The Benefit: Your IT team is free from above tasks, and you’re always running the latest version.  2. The Code Change: C/AL to AL  The “technical stuff”, a necessary evil that will impact your project timeline and/or budget. Also classic NAV uses a coding language called “C/AL.” Microsoft Business Central uses a new language called “AL,” which is “cloud-ready” and “modern.”  What to Expect: If your NAV implementation is heavily customized (and most are), these customizations cannot be “copy and pasted.” They must be “re-written” or “ported” as “Extensions.”  The Impact: Now is the time to clean up those customizations. Do you really need a customization written five years ago? Migration time is a good time to go “standard,” which makes future upgrades easier.  3. The “Extension” Model vs. Object Modification  In previous versions of NAV, developers would often make modifications to the system’s core objects. This would cause problems if they tried to upgrade the system, as these modifications would interfere with new updates from Microsoft.  What to Expect: Business Central utilizes an extension model. This means instead of modifying the code, customizations and add-ons sit on top of the system, stacked on like blocks.  The Benefit: If Microsoft updates Business Central, the extensions will be preserved. This means you will no longer have to re-create customizations every time an update is rolled out.  4. Data Migration: The “Clean Slate” Opportunity  Data migration is usually the biggest concern for a business. You have years of historical data.  What to Expect:  You may not actually need to migrate all that data. While Master Data like Customers, Vendors, and Items is a priority, as is Open Ledger Entries like unpaid invoices, migrating data for the last 10 years of historical data may be unnecessary and expensive.  The Strategy:  Most businesses will end up migrating open data and possibly the last two years of historical data. The older data can be kept in a “read-only” NAV instance for reporting.  5. A Shift in User Experience (UI/UX)  The user interface for Business Central is quite dissimilar from the classic NAV interface.  What to Expect:  The interface is a browser interface that is very similar to Outlook or Office 365. It is a responsive interface, meaning it works well with tablets and smaller screens.  The Adjustment:  You will need to adjust your staff to the new interface. However, as it is a standard Microsoft interface, most users will find it quite intuitive after a short training period.  6. Integration is Native, Not an Afterthought  With NAV systems, integration to Office 365 was sometimes required to be done through third parties or extensive configurations. With Business Central, integration is now native.  What to Expect: Expect to be able to see your Business Central data within Outlook, be able to edit Excel data that is synced to Business Central in real-time and be able to use Power Automate to automate business processes.  The Benefit: No more living in a silo. The sales team can be working in Outlook and be putting data into the ERP system without even realizing it.  7. The Timeline and Process  The typical phases of a migration project are as follows:  Analysis – Reviewing the existing NAV customizations and data.  Code Upgrade – Converting the customizations to AL extensions.  Data Migration – Migrating the data and open entries.  Training – Educating users on the new interface.  Go Live – Switch over.  The project duration for a simple upgrade may be a few weeks, while a complex project with heavy customizations may take several months. The project is full of surprises, and data cleanliness is a problem that may need resolution.  Conclusion: Embrace the Change  Migrating from NAV to Business Central is not only a technical imperative; it is a business enabler. It offers accessibility (work from anywhere), scalability, as well as access to new technologies like Artificial Intelligence and Power BI.  The secret to success is to work with the right experts and see this as an opportunity to improve your business processes, rather than simply moving your old system into the cloud.  Are you ready to future-proof your business? The cloud is waiting. 
Continue Reading
From APIs to AI: How MCP Changes the Way Systems Integrate with Business Central
09
Mar

From APIs to AI: How MCP Changes the Way Systems Integrate with Business Central 

The “Golden Rule” of systems integration has been simple: if you want to talk to Business Central (BC), you use an API. Whether it was OData, SOAP, or even the newer REST endpoints, developers write code to integrate between external systems and the ERP. And it worked. But it was rigid, expensive, and hard to maintain.  But now, we find ourselves at the precipice of an enormous change. With the advent of Generative AI and LLMs, it is no longer sufficient to simply expose an API. We need systems that can understand context, not just exchange data.  Enter The Model Context Protocol (MCP).  In this article, we’re going to explore how MCP is changing the game in terms of Business Central integration.  The Old Way: The “API Spaghetti” Problem  To understand why MCP is a gamechanger, we first need to understand the problems with the status quo.  The pain point here is that it’s a lot of work. Every time you want to do something new like posting a journal entry or checking the customer’s inventory, you have to do it all over again.   Enter MCP: The “USB Port” for AI  MCP can be thought of as a new “standard,” similar in concept to USB and Bluetooth, but for the data systems and AI.  Rather than requiring glue code for every single interaction between the AI and the data systems, the MCP provides a standardized and open-source protocol that allows the AI assistant to query the data systems securely.  In the context of Business Central, the MCP is a dynamic translation layer that allows the AI model to query your ERP in real-time, without requiring you to create a specific API handler.  How MCP Alters Business Central Integrations  So, what are the implications for the BC developer or consultant?  1. “From Hardcoded Endpoints to Dynamic Discovery”  With traditional APIs, the AI is only able to do what you program into it. But what if you have an MCP server connected into Business Central? The AI can now “discover” what’s available.  For example, if the MCP server exposes the Business Central “Customer” table, the AI can automatically determine how to query the No., Name, or Balance fields without you having to write code like get_customer_balance.  2. Context Aware Interactions  Standard APIs are stateless; they don’t have any knowledge of the conversation history.  MCP is built with the goal of being context aware.  Scenario: “Who owes us the most money?”  Traditional: The API may simply return a list of customers.  MCP: The AI can use the protocol to first query the Detailed Cust. Ledg. Entry table, compute the open balances in real-time, and then ask the user, “Do you want me to send a reminder email to the top 3 overdue accounts?” The integration is not just a simple retrieval; the API is participating in the process.  3. Secure, Governed Access  One of the biggest fears of integrating AI with ERP is security. You do not want a chat session with an AI to accidentally change your General Ledger setup.  MCP servers operate locally or in your infrastructure. This means you can use standard BC security permissions. If the user of the AI question being asked does not have permission to DELETE in the Sales Header table, the MCP server will simply not allow it. They bring their standard BC permission set into the AI conversation.  4. Eliminating “Connector Fatigue”  Today, to integrate a niche app into BC, we must develop a connector. With MCP, however, if a third-party app (such as a niche app for inventory scanning or a niche app for human resources) supports the MCP standard, it will instantly connect to your Business Central AI environment.  The Future is “Agentic”  MCP is not just integration; it’s “Agency.”  Business Central was once just a database, just waiting for the application code to tell it what to do. Now, with the protocol, Business Central is an active participant in the world of business intelligence. An AI agent can always monitor your data and only alert you, when necessary, like when the stock level of an item plummets or when the price of the item in a purchase order is wrong.  Conclusion  APIs aren’t going away anytime soon. Business Central will always need OData and REST for rigid system-to-system heavy lifting to integrate between external systems But for the new generation of intelligent automation: Co-pilots, agents, chatbots… the missing piece is the Model Context Protocol. It turns Business Central from a traditional ERP into a smart platform that any AI can talk to.  For developers and architects: the message is clear: Start thinking about context. The end of the era of static integration is near. The era of intelligent agentic integration is upon us. 
Continue Reading
Supercharge Your ERP: The Ultimate Guide to Business Central Integration with AI Tools
02
Mar

Supercharge Your ERP: The Ultimate Guide to Business Central Integration with AI Tools 

In today’s business environment, an ERP solution is more than just an electronic filing cabinet for your invoices and inventory. It is the “nervous system” of your business. However, even a robust solution such as Microsoft Dynamics 365 Business Central has its limitations when operating alone. To fully leverage your data, you need intelligence. By integrating AI services with Business Central (BC), you can move from reactive decision-making to predictive automation. Whether it is predicting cash flow, automating customer service, or analysing market trends, the combination of BC and AI is a gamechanger.  Why Integrate AI with Business Central?  Business Central is great at organizing data, it understands what you sold, to whom, and when it will be delivered. But traditional ERP systems usually need human help to understand the data.  AI bridges the gap. When you integrate AI with BC, you get three major benefits:  Automation of Complex Tasks: Beyond the use of simple macros to cognitive automation (such as matching invoices to purchase orders even when the data is not clean).  Predictive Analytics: Predicting demand based on past data instead of intuition.  Customer Experience: Giving immediate, data-driven answers to customer inquiries.  Top AI Integration Scenarios for Business Central  These are the most compelling ways to integrate Business Central with the world of AI.  1. Microsoft Co-pilot: The Native Revolution  Copilot is not just an AI solution within the Microsoft ecosystem; it must be mentioned in any discussion about AI in Microsoft.  What it does: Copilot can automatically generate marketing emails from your product information in BC, investigate anomalies in your chart of accounts in BC, or summarize your sales reports in natural language.  2. Generative AI for Product Descriptions (ChatGPT/OpenAI)  One of the most popular third-party integrations is linking Business Central to the OpenAI API (through Azure or Power Automate).  The Problem: You must import hundreds of new SKUs. Your warehouse staff is familiar with the technical details, but they’re not copywriters.  The Solution: When a new item is added to BC, a workflow fires off an AI request. The AI uses the technical details (colour, size, material) and auto-generates a catchy, SEO-optimized product description, which is then automatically posted back to the item card.  3. AI-Powered Customer Support  Linking BC to AI-powered helpdesk software (such as Zendesk AI or custom chatbots) enables a closed-loop support process.  The Problem: A customer submits a support request asking, “Where is my order?”  The Solution: Rather than a human support rep logging into BC to check the status, an AI chatbot queries the Business Central sales ledger in an instant. It pulls the shipment tracking number and estimated delivery date and responds to the customer in seconds.  The Result: Support costs decrease, while customer satisfaction ratings increase.  4. Predictive Sales and Cash Flow (Power BI + Azure AI)  While Business Central has reporting capabilities, combining it with Power BI and Azure Machine Learning takes forecasting to the next level.  The Problem: You must forecast next month’s cash flow to effectively manage payroll.  The Solution: Data is pulled from BC into Azure, where ML learns from seasonality, payment patterns, and economic data. This produces a live forecast in Power BI that automatically alerts you to possible cash flow issues weeks before they occur.  5. Intelligent Document Processing  Manual processing of vendor invoices is a chore. While BC has OCR functionality, combining it with AI software (such as UiPath or ABBYY) enables a “touchless” AP process.  The Solution: This software can read PDFs, interpret line-item data regardless of the invoice layout, and match them to Purchase Orders in BC before automatically posting them for payment.  How to Integrate: The Technical “Glue”  But how do you integrate these tools? The Microsoft platform makes this surprisingly easy.  Power Automate: This is the most popular tool for integration. You can set up “Flows” that are triggered when data in BC changes (for example, a new customer is entered) and send that data to an AI service (such as OpenAI or Azure Cognitive Services) and then push the result back.  APIs: Business Central has excellent REST APIs. If you are using a third-party AI service, they probably have a standard connector for Microsoft Dynamics 365.  Power Apps: If you want to build a custom internal interface, you can set up an app that retrieves data from BC but uses an AI model in the backend to help users make decisions.  Challenges to Consider  While the advantages are obvious, a successful integration process involves planning for the following:  Data Quality: AI is only as good as the data it is trained on. If your BC data is riddled with duplicates and inaccuracies, your AI will hallucinate or provide poor recommendations. “Clean data” is a necessity.  Security & Compliance: Make sure that any third-party AI service you integrate with is compliant with industry regulations. Sharing financial information with public AI services requires a strict governance model.  Change Management: Employees may worry that AI is coming to replace them. Frame AI as a “co-pilot” that will take the mundane tasks out of their job, freeing them up to focus on high-level tasks.  The Future is Integrated  Business Central is a powerful platform, but AI is the engine that propels it forward. The future of ERP is not simply “recording” business; it is “sensing” and “predicting” business.  Whether you begin with small-scale integration, such as automated product descriptions, or go all-in with predictive cash flow models, integrating AI services with Business Central is no longer a vision of the future, it is a necessity. 
Continue Reading
Transforming ERP into a Communication Hub: The Power of Email in Dynamics 365 Business Central
23
Feb

Transforming ERP into a Communication Hub: The Power of Email in Dynamics 365 Business Central 

In today’s enterprise, data fragmentation is the major factor that hinders efficiency in enterprise operations. Traditionally, Enterprise Resource Planning (ERP) solutions have served as separate repositories of enterprise financial and operational data. However, as enterprise processes become more digital, there is an increased need for a unified workflow.  Microsoft Dynamics 365 Business Central resolves this challenge through its evolution from a static database into a dynamic communication powerhouse. It achieves this through a deep integration of the email functionality into the core of the system, thereby bridging the information gap between operations.  Following are the details on how Microsoft Dynamics 365 Business Central can optimize business communication:  1. Seamless Ecosystem Integration  The strength of Business Central resides within its native integration with the Microsoft 365 ecosystem. This provides a level of synergy unmatched by the competition that streamlines the organization by removing inefficient “context switching” experiences. Context switching is the resultant productivity cost of switching between disparate applications.  Therefore, with the integration of Microsoft Outlook and Business Central, organizations can achieve a bi-directional flow of information:  Visibility within Outlook: Users can see their financial information, customer history, and inventory levels in their email inbox without having to log in to a separate ERP.  Action within ERP: On the other hand, users can write and send emails through Business Central customer and vendor cards. This would provide a unified interface for various applications and ensure employee access to the context needed for communication effectively.  2. Automating Document Distribution  Manual intervention in document processing is a time-consuming process because it is prone to human error. The process of relying on humans to perform tasks such as exporting invoices, saving them as PDFs, and then attaching them to emails is an outdated process.  Business Central performs this critical business function through automated workflow configurations:  Automated Dispatch: Sales invoices, purchase orders, and quotes can be set up to automatically dispatch and send themselves via email after posting.  Scheduled Reporting: Organizations can use this feature by automating reports, such as statements or overdue notifications, promoting regular cash flow management. This can help businesses utilize their human capital effectively by focusing on important tasks rather than routine ones.  3. Centralized Correspondence and Auditability  When it comes to highly regulated industries and complex B2B scenarios, it’s no longer optional to have an entire audit trail of communications. Multiple inboxes make it virtually impossible to keep track of what was said and when.  Business Central centralizes the communication aspect by storing all the email interactions in the relevant Contact or Vendor card. This allows a chronological record of all the interactions, documents sent, and documents received.   4. Standardization and Brand Consistency  For all growing businesses, it is important that a consistent brand is maintained, especially with respect to interactions with customers. Ad hoc emailing often results in variable email formats.  Business Central enforces standardization through:  Document Layouts: Users can create professional document templates directly in Microsoft Word. This lets them ensure all invoices and statements are in corporate brand format.  Email Templates: Standardized text for confirmation emails, reminders, and marketing emails helps ensure that consistency is maintained in the tone of voice, regardless of who among employees is sending them.  Conclusion  The modern Enterprise Resource Planning system needs to do more than just store data; it also needs to be able to allow the flow of this information. Within this context, organizations can break down data silos by embedding email capabilities within Dynamics 365 Business Central. When email functionality is integrated into the system, the system itself converts from a passive ledger system to a more active system. 
Continue Reading