Microsoft Great Plains Remote Support - overview

Understanding Great Plains Support Landscape

Microsoft Great Plains has evolved into a cornerstone for mid‑market ERP, powering companies across a range of industries from manufacturing and retail to professional services. Its appeal lies in a combination of robust functionality - finance, supply chain, operations - and the flexibility that comes with a strong developer community. Because it sits at the heart of many day‑to‑day business processes, any interruption or inefficiency can ripple through the organization, impacting cash flow, compliance, and customer satisfaction.

For mid‑size firms, the ideal scenario is a blend of in‑house expertise and vendor support that keeps costs manageable while maintaining system stability. Typically, the IT team owns a solid foundation in SQL, database administration, and application troubleshooting. At the same time, accounting and finance staff are comfortable navigating the user interface, interpreting reports, and entering data. They may only need a few touch‑points when a new release arrives: updated fields, changes in report formats, or new workflow options. This setup reduces the need for expensive on‑site consulting engagements, allowing the business to reallocate resources toward growth initiatives rather than ongoing support.

However, even the most proficient teams will encounter scenarios where deeper intervention is necessary. A critical upgrade can expose latent bugs, compatibility issues with custom reports, or integration hiccups with legacy systems. In such cases, bringing in an external consultant can accelerate resolution, minimize downtime, and safeguard against costly post‑upgrade surprises. The decision hinges on three factors: the complexity of the customizations, the criticality of the user base, and the financial buffer available for support services.

Financially, the cost of consulting can appear steep - four‑hour visits might run close to $200 per hour. Yet, when weighed against the potential loss of revenue from extended downtime or the expense of fixing problems after they occur, this investment often pays for itself. In addition, the knowledge transfer that occurs during these engagements can upskill the internal team, creating a stronger foundation for future upgrades and troubleshooting.

Another consideration is the evolving relationship between Microsoft and its partners. The ecosystem is shifting from a reliance on high‑volume, one‑time consulting projects to a model that encourages ongoing engagement through support and enhancement plans. This transition benefits organizations that are willing to partner with vendors who can provide consistent, proactive maintenance while keeping total cost of ownership low.

In summary, the Great Plains support landscape demands a balanced approach: leverage internal talent for routine tasks, engage external experts for critical upgrades and complex customizations, and choose partners who understand the nuances of mid‑market operations. By aligning support strategy with business priorities, firms can keep their ERP environment healthy, responsive, and cost‑effective.

Choosing the Right Partner: Local vs Nationwide

When it comes to selecting a partner for Great Plains, the debate often centers around local versus nationwide vendors. Each type of partner brings distinct advantages and potential pitfalls that can influence both the quality of service and the overall budget.

Local partners are embedded in the community. They know the regional market, understand the specific challenges of nearby industries, and can often respond quickly to urgent issues. Their marketing tactics - trade shows, cold‑call sales teams, in‑person demos - create a tangible presence. However, this visibility comes at a price. The costs associated with maintaining a full‑time sales force, traveling for presentations, and offering on‑site support inflate hourly rates. When a local partner pitches a migration or upgrade, they may bundle the work with additional services to justify a premium price. Their focus on winning a deal can also result in a sales‑driven approach, which may not always align with the client’s long‑term needs.

Nationwide partners, on the other hand, adopt a more digital‑first strategy. They rely on online marketing, webinars, and remote consultations to reach a broader audience. Their overhead is lower because they don’t need to support multiple physical locations or travel extensively. This lean model often translates into more competitive rates for basic consulting and support tasks. Moreover, many nationwide vendors operate on a subscription basis, offering access to a range of services - including training, monitoring, and scheduled maintenance - at a predictable cost.

However, remote partners may not always match the depth of local expertise, especially when it comes to complex customizations or legacy integrations. Their team may handle a wider array of issues across diverse industries, which can dilute the specialization that a local partner offers for a specific region or vertical. If your organization requires daily interaction with a developer who understands the nuances of your custom workflows, a partner with a dedicated, in‑depth specialization may be preferable.

From a cost perspective, the decision often hinges on the size of the user base and the level of customization. A company with 20 or fewer users and modest customizations may find that a nationwide partner offers sufficient support for routine maintenance and scheduled upgrades. For firms with more extensive custom development - especially those that rely heavily on ReportWriter modifications or proprietary modules - a local partner with a strong development focus can deliver faster, more precise fixes.

In practice, many organizations adopt a hybrid model. They partner with a nationwide vendor for ongoing support contracts, training, and routine updates while engaging a local developer for critical customization or migration projects. This approach combines the economies of scale offered by a national partner with the tailored expertise of a local team, striking a balance between cost and quality.

When Customization or Migration Demands a Consultant

Not every upgrade or migration is created equal. Several specific scenarios warrant the involvement of a dedicated consultant to mitigate risk and ensure a smooth transition.

First, consider the presence of Dexterity customizations. Dexterity scripts can deeply embed logic within the Great Plains data model. When a new version alters the underlying database schema, these scripts may break or behave unpredictably. A consultant who has experience in Dexterity can audit and re‑engineer these scripts, guaranteeing that custom business rules continue to function after the upgrade.

Second, migrating from non‑Microsoft databases - such as Pervasive or Ctree - to Microsoft SQL Server or SQL Server Express (formerly MSDE) presents a significant technical challenge. The lack of built‑in migration tools from Microsoft means that the process must be orchestrated manually or through third‑party utilities. A consultant familiar with these migrations can map data types, re‑create indices, and validate data integrity, reducing the risk of corrupted or missing records.

Third, extensive modifications to ReportWriter reports indicate a highly customized reporting layer. Each change, from added fields to altered layouts, increases the complexity of the upgrade path. A consultant can review the report set, identify dependencies, and adjust report definitions to align with new data structures, preventing runtime errors and ensuring continuity for end users.

Fourth, organizations using legacy Great Plains releases - such as Dynamics or Enterprise 6.0 - face a unique situation. Microsoft’s official support for these older versions has ended, meaning that the vendor can no longer provide patches or assistance. In such cases, a consultant can bridge the gap by planning a phased migration to a supported release, preserving critical data and processes along the way.

Finally, for companies with more than 20 users, an upgrade that targets the entire user base often needs to be scheduled over a weekend to minimize business disruption. The stakes are higher: if the upgrade fails, the entire organization can be halted. A consultant brings the expertise to create a detailed rollback plan, perform pre‑upgrade testing, and monitor the live environment during the cutover, ensuring that any unforeseen issues are addressed immediately.

In each of these scenarios, the consultant’s role extends beyond mere code modifications. They provide project management, risk assessment, and knowledge transfer, enabling the internal team to handle routine issues post‑upgrade. By investing in a consultant at the right time, organizations protect themselves from costly downtime and maintain the integrity of their ERP environment.

Cost‑Effective Upgrade Strategies

Upgrade projects are often the biggest drivers of cost for Great Plains users. Yet, with a strategic approach, companies can keep upgrade expenses in check while still reaping the benefits of new features and security patches.

First, work closely with a partner that offers promotional pricing for migrations and upgrades. Many Microsoft Business Solutions VARs have agreements that allow them to negotiate discounted rates during specific periods. By aligning the upgrade timeline with these promotional windows, firms can secure substantial savings. The key is to avoid being pressured into a full‑priced package; a knowledgeable partner will highlight the actual cost components and negotiate only the parts that add value to the business.

Second, consider the benefits of a subscription‑based support plan. Microsoft’s Enhancement Plans provide access to the latest releases, support tickets, and ongoing training. Rather than paying a lump sum for each new version, an organization can budget a predictable annual fee that covers the entire upgrade cycle. This approach spreads costs over time and eliminates the shock of a one‑off expense.

Third, plan the upgrade in phases whenever possible. Instead of a full system overhaul, test new features in a sandbox environment, validate customizations, and roll out incrementally. This staged approach reduces the risk of major disruptions and allows the team to catch issues early, which is cheaper than fixing them after the entire user base is impacted.

Fourth, leverage internal resources for preparatory tasks. Backing up databases, cleaning up obsolete records, and reviewing custom code can all be performed by the in‑house IT staff. By taking care of these tasks internally, companies reduce the scope of work that the consultant needs to handle, translating into lower fees.

Lastly, maintain an open line of communication with the partner’s sales and technical teams. Regular check‑ins keep everyone aligned on timelines, deliverables, and budget constraints. When stakeholders understand the financial implications of each decision, they are less likely to approve costly add‑ons that do not provide direct business value.

By combining promotional pricing, subscription support, phased rollouts, internal preparation, and proactive communication, firms can manage upgrade costs effectively while keeping their Great Plains environment up to date and secure.

Partnering with Alba Spectrum Technologies

Alba Spectrum Technologies has positioned itself as a national specialist in Microsoft Great Plains and CRM solutions. With offices spread across major U.S. markets - including Chicago, California, Texas, New York, Georgia, and Florida - the company offers a geographically broad reach combined with deep technical expertise.

The firm’s leadership, headed by Chief Technology Officer Andrew Karasev, brings a track record in Dexterity scripting, SQL database management, C#.NET development, Crystal Reports, and Microsoft CRM SDK integration. This breadth ensures that clients receive comprehensive support that covers everything from database optimization to custom front‑end development.

Alba Spectrum’s consulting model prioritizes practical outcomes over generic service. Clients typically experience a structured assessment phase where current customizations, data integrity, and integration points are reviewed. This assessment feeds into a tailored upgrade plan that aligns with the business’s operational rhythms.

Because the company has a national presence, it can respond to on‑site needs without incurring the travel overhead that some local VARs face. For firms that require face‑to‑face collaboration on complex migrations or report rewrites, Alba Spectrum can deploy a consultant to the office for the duration of the project, providing the personal touch that remote teams may lack.

For companies that rely heavily on custom reports or proprietary modules, Alba Spectrum’s development team can work closely with the client’s internal staff. This collaboration fosters knowledge transfer, enabling the business to manage routine maintenance internally after the project’s conclusion.

To learn more about how Alba Spectrum can help you navigate Great Plains upgrades, customizations, and remote support, visit