mark mckinney
Forum Replies Created
-
Organizations can design a cost-optimized and highly resilient architecture by balancing performance, reliability, and expenses. The goal is to ensure systems remain available during failures while avoiding unnecessary costs.
A cost-effective approach starts with using cloud resources efficiently. Organizations should choose the right-sized computing, storage, and networking services based on actual demand. Features such as auto-scaling allow resources to increase during peak traffic and decrease during low usage, reducing operational costs. Regular monitoring and cost analysis also help identify unused or underutilized resources.
To achieve high resilience, critical applications should be deployed across multiple availability zones or regions. This ensures that if one location experiences an outage, services can continue running from another location. Data should be backed up regularly and replicated across different locations to prevent data loss. Organizations should also implement disaster recovery plans and test them periodically to ensure quick recovery during unexpected events.
Using load balancers can distribute traffic across multiple servers, preventing a single point of failure. Automated monitoring and alerting systems help detect issues early so that corrective actions can be taken before users are affected. Security measures such as encryption, identity management, and regular updates further strengthen the architecture and reduce risks.
Finally, organizations should adopt a well-architected framework that continuously reviews performance, reliability, security, and cost efficiency. By combining efficient resource utilization, automation, backup strategies, redundancy, and proactive monitoring, businesses can build an architecture that is both resilient and economical.
-
It depends on the business scenario, but many users initially find Order Planning in Dynamics 365 Business Central (BC) a bit overcomplicated.
The main reason is that Order Planning combines several factors at once, such as demand, inventory levels, lead times, reorder policies, safety stock, and existing supply orders. For organizations moving from spreadsheets or simpler ERP systems, the planning worksheet can feel overwhelming because a single planning suggestion may be influenced by multiple settings spread across items, vendors, locations, and SKUs.
That said, the complexity often comes from the setup rather than the day-to-day use. Once parameters like reordering policy, lead time calculation, and lot sizing are configured correctly, the system can generate highly accurate supply suggestions and significantly reduce manual planning effort.
A common mistake is trying to understand planning results without first reviewing the item planning settings. When those settings are inconsistent, the planning worksheet may produce recommendations that seem confusing or incorrect.
My view is that BC Order Planning is powerful but not always intuitive. For smaller businesses with straightforward inventory requirements, it can feel more complex than necessary. For companies managing multiple locations, hundreds of SKUs, or variable demand, the additional complexity usually brings real value through better inventory control and fewer stockouts.
So, I wouldn’t call it overcomplicated by design, but it definitely has a learning curve and requires careful setup to deliver the expected results.
-
Weāve been using Copilot in Dynamics 365 mainly to save time on routine work and help teams focus on higher-value tasks.
In Dynamics 365 Sales, Copilot helps sales reps by summarizing customer interactions, drafting follow-up emails, and preparing meeting notes. Instead of spending time reviewing long account histories, the team can quickly understand customer needs and next steps.
In Customer Service, Copilot assists agents by generating response suggestions, summarizing support cases, and finding relevant knowledge articles. This helps reduce response times and improves customer satisfaction.
For marketing teams, Copilot is useful for creating email content, campaign ideas, customer segment descriptions, and performance summaries. It speeds up content creation while still allowing marketers to review and personalize the output.
In Business Central and ERP processes, Copilot helps users analyze financial data, identify trends, generate reports, and ask questions using natural language. Rather than manually building reports, users can quickly get insights about sales performance, inventory levels, or cash flow.
Another practical use case is meeting preparation. Copilot can summarize previous communications, outstanding opportunities, and key customer information before calls. This helps teams enter meetings better prepared.
One thing we’ve learned is that Copilot works best as a productivity assistant rather than a replacement for human decision-making. It helps with drafting, summarizing, analyzing, and finding information quickly, but users still review and validate the results.
Overall, the biggest benefits we’ve seen are reduced administrative work, faster access to information, improved productivity, and more time for customer-facing and strategic activities. For most users, even saving 15-20 minutes a day adds up to significant efficiency gains over time.
-
From my experience, D365 F&O projects rarely fail because of the software itself. Most failures happen due to poor planning, process gaps, or lack of user adoption.
Here are the most common reasons:
Unclear Business Requirements
Teams start implementation without fully defining processes and expectations.
Avoid it: Conduct detailed discovery workshops and get stakeholder sign-off before design begins.
Trying to Customize Everything
Organizations often try to replicate every legacy system process in D365.
Avoid it: Adopt standard D365 functionality wherever possible and customize only when there is a strong business justification.
Poor Data Migration
Inaccurate, duplicate, or incomplete legacy data creates issues after go-live.
Avoid it: Clean, validate, and test data migration multiple times before deployment.
Lack of User Training
Users resist the new system because they don’t understand how to use it.
Avoid it: Invest in role-based training, user acceptance testing (UAT), and change management.
Weak Project Governance
Delayed decisions, scope creep, and conflicting priorities can derail timelines.
Avoid it: Establish a strong governance structure with clear ownership and decision-making processes.
Insufficient Testing
Teams rush through testing to meet go-live deadlines.
Avoid it: Perform end-to-end, integration, performance, and UAT testing thoroughly.
Underestimating Change Management
Technology changes are easier than people changes.
Avoid it: Engage business users early, communicate benefits, and create change champions.
-
Yes, many Business Central users find Order Planning somewhat complicated, especially when they first start using it.
The complexity usually comes from the number of planning parameters involved, such as reorder policies, safety stock, lead times, lot accumulation periods, dampeners, and planning worksheets. If these settings are not configured correctly, the planning results can be confusing and may generate unexpected suggestions.
That said, Order Planning is designed to handle complex supply chain scenarios. For organizations with multiple items, vendors, locations, and varying demand patterns, the functionality can be extremely powerful. Once the planning setup is properly configured, it can significantly reduce manual purchasing and replenishment efforts.
A few things that typically make Order Planning easier to manage are:
Keeping replenishment policies simple whenever possible.
Reviewing item planning parameters regularly.
Using Planning Worksheets to understand why suggestions are generated.
Testing planning changes in a sandbox environment before applying them in production.
Ensuring lead times and inventory data are accurate.
In my experience, the challenge is often not the planning engine itself but the initial setup and understanding of how different planning parameters interact. Users who invest time in configuring and learning the planning logic usually find it quite effective, while those expecting a “set it and forget it” solution may perceive it as overly complicated.
So, I would say Order Planning in Business Central is powerful rather than overly complicated, but it does have a learning curve and requires careful configuration to deliver reliable results.
-
If I were advising a Dynamics GP customer on an upgrade path, my first recommendation would generally be Dynamics 365 Business Central. For many small and mid-sized organizations, Business Central offers the right balance of functionality, scalability, and ease of adoption. It modernizes core ERP processes such as finance, sales, purchasing, inventory, and reporting while providing the benefits of a cloud-based platform.
In my experience, many GP customers are looking for a solution that supports future growth without introducing unnecessary complexity. Business Central often fits that requirement well. It also integrates seamlessly with Microsoft 365, Power BI, and Power Automate, helping organizations improve productivity and reporting capabilities.
That said, Dynamics 365 Finance & Operations (F&O) is a strong option for larger enterprises with complex business processes, multiple legal entities, advanced manufacturing, or global operations. The choice ultimately depends on the organization’s size, operational complexity, and long-term business goals.
I have also seen discussions and customer success stories from partners like Alletec, where the focus is not simply on migrating from GP but on evaluating business requirements first and then recommending the most suitable Dynamics 365 platform. I believe that approach is important because every GP customerās journey is different.
Overall, my view is that Business Central is the preferred path for most GP customers, while F&O is best suited for organizations with more sophisticated enterprise-level requirements and scalability needs.
-
Hi Lloyd,
We went through a similar evaluation after being on Dynamics SL for many years. Overall, the biggest challenge wasn’t the software migration itselfāit was rethinking existing business processes and deciding which customizations were still truly needed.
Data migration took more effort than expected, especially around historical project data, custom fields, and reporting requirements. Master data was relatively straightforward, but cleaning old or inconsistent data before migration became a significant task.
Reporting was another area that required attention. Many of our users had become comfortable with SL reports and Excel-based processes. While modern ERP platforms offer more powerful reporting and analytics, recreating some legacy reports and validating the numbers took time.
Regarding customizations, we discovered that several custom developments had been built over many years to compensate for limitations or unique business requirements. During the evaluation process, we found that some could be replaced with standard functionality, while others required additional configuration or extensions.
From a change management perspective, user adoption was probably the most disruptive element. People had been using the same screens and workflows for years, so training and communication were critical. The organizations that seem to have the smoothest transitions are the ones that invest early in user engagement rather than treating the project as purely a technical migration.
My recommendation would be to start with a thorough assessment of:
Current customizations
Integrations
Reporting requirements
Historical data retention needs
Business processes that have evolved over time
You’ll likely find that the migration is as much a business transformation project as it is an ERP replacement project.
Best of luck with the evaluation. SL has served many organizations well, but planning early and understanding your requirements in detail will make the transition much smoother when the time comes.
-
Vendor management is far more than maintaining supplier records and processing invoices. In Microsoft Dynamics 365 Business Central (BC), organizations have access to a wide range of features that can help streamline procurement processes, improve supplier relationships, and enhance financial control. The real question is whether businesses are using these capabilities to their full potential.
One of the most important aspects of effective vendor management is maintaining accurate vendor master data. Business Central allows companies to centralize vendor information, including contact details, payment terms, shipping information, tax details, and transaction history. Keeping this data updated ensures smoother procurement operations and reduces errors that can lead to delayed payments or order discrepancies.
Another area where many organizations fall short is vendor performance monitoring. Business Central provides visibility into purchasing history, delivery timelines, and spending patterns. By analyzing this information regularly, procurement teams can identify high-performing suppliers, negotiate better terms, and reduce dependency on vendors that consistently fail to meet expectations. Data-driven vendor evaluations can significantly improve supply chain reliability and operational efficiency.
Automation is another key capability that often remains underutilized. Business Central can automate purchase approvals, invoice processing, and payment workflows. Automating routine tasks not only reduces administrative workload but also minimizes the risk of human error. Employees can then focus on strategic procurement activities rather than manual data entry and repetitive processes.
Financial management is closely tied to vendor management. Business Central enables businesses to track outstanding balances, payment schedules, discounts, and credit limits. Organizations that actively monitor these metrics can improve cash flow management while maintaining positive supplier relationships. Taking advantage of early-payment discounts and avoiding late-payment penalties can have a direct impact on profitability.
Vendor categorization is another best practice that can unlock additional value. Segmenting vendors based on factors such as spend volume, strategic importance, geographic location, or product category helps organizations make more informed sourcing decisions. Business Central supports this level of organization, making it easier to manage procurement strategies and vendor relationships effectively.
Collaboration between procurement and finance teams is equally important. Since Business Central integrates purchasing and financial data within a single platform, stakeholders gain a unified view of supplier transactions and commitments. This transparency improves decision-making and ensures better alignment between purchasing objectives and financial goals.
Additionally, organizations should regularly review purchasing trends and supplier performance reports available in Business Central. These insights can reveal opportunities for cost optimization, supplier consolidation, and process improvement. Companies that proactively use reporting and analytics capabilities are often better positioned to respond to changing market conditions and supply chain challenges.
-
In my experience, D365 F&O projects rarely fail because of the software itself. Most issues come from poor planning, unrealistic expectations, and lack of business involvement.
One of the biggest reasons for failure is unclear requirements. Organizations often start implementation without fully defining their business processes, which leads to scope changes, delays, and budget overruns. Another common mistake is over-customization. Many companies try to make D365 F&O work exactly like their legacy system instead of adopting standard functionality. This increases complexity and creates challenges during future upgrades.
Data migration is another major risk area. If customer, vendor, inventory, or financial data is inaccurate or incomplete, users quickly lose confidence in the new system. Similarly, insufficient testing can cause critical issues to appear only after go-live, impacting daily operations.
A factor that is often overlooked is user adoption. Even the best-designed solution can struggle if end users are not involved in workshops, testing, and training. Resistance to change is one of the biggest challenges in ERP implementations. When people don’t understand the benefits of the new system, they often continue using old processes or spreadsheets.
How to Avoid These Challenges
Clearly define business requirements before starting configuration.
Follow standard D365 F&O functionality wherever possible.
Clean and validate data before migration.
Involve business users throughout the project lifecycle.
Allocate enough time for end-to-end testing and User Acceptance Testing (UAT).
Invest in training, communication, and change management from the beginning.
-
Organizations need an IT architecture that is both cost-effective and reliable. A cost-optimized and highly resilient architecture helps businesses reduce expenses while ensuring that systems remain available even during unexpected failures.
1. Use Cloud Resources Wisely
Cloud platforms allow businesses to pay only for the resources they use. Organizations can scale resources up during peak demand and scale them down when demand is low. This helps avoid unnecessary infrastructure costs while maintaining performance.
2. Build for High Availability
To minimize downtime, critical applications should be deployed across multiple servers or locations. If one server fails, another can continue running the application. This ensures business continuity and improves customer experience.
3. Automate Processes
Automation reduces manual effort and operational costs. Automated monitoring, backups, updates, and resource management help teams work more efficiently while reducing the risk of human errors.
4. Implement Regular Backup and Disaster Recovery
Businesses should regularly back up important data and have a disaster recovery plan in place. In case of system failures, cyberattacks, or natural disasters, data can be restored quickly, minimizing disruptions.
5. Optimize Storage and Computing Costs
Organizations should regularly review their infrastructure usage and remove unused resources. Choosing the right storage options and computing services can significantly reduce operational expenses without affecting performance.
6. Monitor Performance Continuously
Continuous monitoring helps identify issues before they become major problems. Businesses can track system health, resource utilization, and application performance to ensure optimal operation and avoid unexpected outages.
