Dynamics GP Support, Customization & Integration
Keep complex Dynamics GP environments supportable—and make the next ERP decision on fit.
Stabilize, maintain and extend Dynamics GP while making customizations, integrations and reporting logic visible enough to support a deliberate move to Business Central, NetSuite or another suitable ERP when the time is right.
A defined first step
Start with a Dynamics GP technical assessment.
Bring the GP version, affected modules, customization inventory and a description of the operating problem. Share sanitized error examples before arranging controlled access.
Agree an assessment covering dependencies, support risks and prioritized stabilization or extension work. The proposed output is a findings summary and a scoped next-step plan; migration remains a separate decision.
Scope, access, deliverables, fees and timing are agreed before work begins. Remote delivery arrangements include working-hour overlap, review points and named decision owners.
Discuss the assessment scopeBringing us into an existing consultancy engagement? Review specialist delivery for ERP consultancies.
Watch • 2 minutes
Still running Dynamics GP?
See how Aurosten approaches troubleshooting, customizations, integrations and planning your next step.
Playing this video connects to YouTube.
GP remains a live operating system
Support the system in front of you while keeping the future decision open.
A heavily customized GP estate can contain years of accounting decisions, integrations and operational rules. Those dependencies need engineering ownership whether GP is retained, upgraded, connected to newer systems or replaced.
- A heavily customized GP environment still runs critical finance and operating processes, but the original developers or documentation are no longer available.
- Posting, inventory, manufacturing, project, service or intercompany issues cross module, SQL, customization and third-party product boundaries.
- Dexterity, Modifier/VBA, .NET, eConnect or SQL components need diagnosis, maintenance, controlled enhancement or replacement.
- Salesforce, EDI, commerce, banking, tax, payroll or warehouse integrations fail silently or depend on manual correction.
- The organization needs to compare Business Central, NetSuite or another ERP without assuming that one target fits every process.
Techno-functional scope
Connect module behavior, custom code, data and business controls.
Operate GP safely
Stabilize modules, integrations, reporting, environments and operating procedures while preserving business continuity and audit evidence.
Recover custom engineering
Inventory source, dictionaries, forms, reports, assemblies, SQL objects, schedulers and deployment dependencies before changing inherited logic.
Choose the next state
Compare retain, upgrade, integrate, coexist, replatform and retire options against process fit, data, controls, customization and total transition risk.
GP modules and operating problems
Work across finance, distribution, operations and the custom layers between them.
Financial and multi-company operations
Connect accounting intent to GP configuration, transactions and control evidence.
- General Ledger, Payables, Receivables, Bank Reconciliation, Fixed Assets and Cash Flow
- Multicurrency, Analytical Accounting, deferrals, allocations and period-end processing
- Multi-company, intercompany, consolidations and shared-master-data behavior
- Posting setup, batches, distributions, subledger reconciliation and audit support
Distribution, inventory and operations
Trace transactions through the modules where operational and financial state meet.
- Sales Order Processing, Purchase Order Processing and Inventory Control
- Pricing, allocations, fulfillment, returns, landed cost and item tracking
- Inventory costing, historical transactions, valuation and reconciliation
- Manufacturing, Project Accounting, Field Service and adjacent industry solutions
Troubleshooting and recovery
Diagnose repeatable causes across GP, SQL Server, custom code and operating practice.
- Posting interruptions, stuck batches, reconcile/check-links findings and data inconsistencies
- Performance, blocking, SQL jobs, maintenance, environment health and upgrade readiness
- Security, dictionaries, forms, reports, client/runtime and deployment issues
- Evidence preservation, safe correction, validation and prevention runbooks
Customization maintenance
Keep important custom behavior supportable without treating every customization as permanent.
- Dexterity dictionaries, sanScript, Modifier/VBA and Visual Studio Tools for .NET
- Forms, windows, events, reports, chunk deployment, source control and build recovery
- Extender, Power Tools, custom utilities, Windows services and scheduled processes
- Retain, repair, redesign, replace or retire decisions for each material dependency
Integration and data engineering
Make cross-system transactions observable, recoverable and reconcilable.
- eConnect, Dynamics GP Web Services, Integration Manager, SmartConnect and Scribe
- SQL staging, .NET services, REST or SOAP APIs, files, EDI and message-based patterns
- Salesforce account, customer, order, invoice and payment-related integration flows
- Logging, alerting, retry, duplicate control, exception ownership and reconciliation
ERP transition and coexistence
Plan from the actual GP estate rather than from a predetermined product destination.
- Business Central, NetSuite or other ERP fit-gap and target operating-model review
- Customization, report, integration and data-history disposition
- Phased coexistence, interface transition, archive and decommissioning boundaries
- Trial conversion, reconciliation, business acceptance and cutover recovery criteria
Development and integration stack
Maintain the old layers responsibly and use modern interfaces where they fit.
Native GP development
Use the development layer that matches the existing implementation and its support boundary.
- Microsoft Dexterity and sanScript
- Modifier with VBA and Report Writer
- Visual Studio Tools for Microsoft Dynamics GP with C# or VB.NET
- Extender, Power Tools and release-managed dictionary deployment
Integration interfaces
Select supported interfaces and explicit contracts instead of coupling every flow directly to database tables.
- eConnect, Dynamics GP Web Services and Integration Manager
- SmartConnect, Scribe, .NET services, REST/SOAP APIs, files and EDI
- Salesforce REST and Bulk APIs for governed CRM data exchange
- NetSuite SuiteTalk web services and controlled migration or coexistence interfaces
SQL, reporting and diagnostics
Use database knowledge to diagnose and reconcile without bypassing application controls casually.
- SQL Server diagnostics, query plans, blocking, jobs, backups and environment checks
- SmartList and SmartList Builder, SSRS, Excel, Power BI, Jet Reports and Solver
- Schema discovery, data profiling, controlled staging, extracts and reconciliation
Target-platform engineering boundary
Treat the destination as its own governed platform, not a renamed GP customization estate.
- Business Central AL extensions, APIs, upgrade-safe design and Power Platform where appropriate
- NetSuite SuiteCloud, SuiteScript and SuiteCloud Development Framework where target specialists are engaged
- Version control, repeatable deployment, test evidence and operational handoff
Representative ecosystem
Account for the products and platforms connected to GP.
Product names identify systems that may be encountered or evaluated. They do not imply partnership, reseller status, certification or endorsement.
Nolan and intercompany products
Representative systems include Nolan Advanced Bank Reconciliation and Nolan InterCompany products; product names identify technologies only and do not imply a partnership or endorsement.
Integration and data movement
Representative products include eOne SmartConnect and Popdock, Scribe, Integration Manager and controlled custom services.
Multi-entity, payments and compliance
Representative products include Binary Stream Multi-Entity Management, Mekorma, Tipalti, HighRadius, Avalara and Greenshades.
CRM and customer operations
Representative connections include Salesforce Sales Cloud and Service Cloud, custom CRM platforms and governed customer-master synchronization.
Service, EDI and commerce
Representative products include WennSoft, TrueCommerce, SPS Commerce, Shopify, BigCommerce and marketplace connectors.
ERP destinations and adjacent platforms
Transition analysis may include Dynamics 365 Business Central, Oracle NetSuite or another ERP selected through fit-gap evidence; inclusion does not claim full implementation coverage for every platform.
Engineering controls
Change GP without losing the evidence needed to support it.
Preserve evidence first
Capture version, source, deployment, configuration, schema, logs and representative transaction evidence before broad change.
Respect application boundaries
Use supported interfaces where practical and treat direct SQL correction as a controlled exception with validation and recovery.
Separate product fit from migration momentum
Compare candidate ERPs against business requirements before committing customizations or data to a target.
Prove transaction outcomes
Validate normal and failure paths, reconcile financial and operational state, and leave support ownership explicit.
Support and transition method
Stabilize first, compare targets with evidence, then transition deliberately.
Discover
Inventory modules, companies, customizations, reports, integrations, data and operating dependencies.
Stabilize
Contain urgent failures, restore repeatable operation and preserve evidence for root-cause work.
Engineer
Repair or enhance bounded components with source, deployment, validation and rollback controls.
Compare
Evaluate retain, upgrade, coexist and target-ERP options against explicit fit and risk criteria.
Transition
Move data, rules and interfaces through rehearsed increments with reconciliation and acceptance.
Operate
Document monitoring, exceptions, recovery, ownership and the next planned decision point.
Useful outputs
Leave the GP estate more understandable, supportable and decision-ready.
- GP environment, module, customization and integration inventory
- Stabilization findings, prioritized remediation and support runbook
- Source, build, deployment and dependency recovery record
- Integration contract, exception model and reconciliation controls
- Destination-neutral ERP fit-gap and dependency disposition
- Phased transition, coexistence, acceptance and recovery plan
Common questions
Separate current support needs from the eventual ERP decision.
Can Dynamics GP be supported while we decide what comes next?
Yes. Stabilization, upgrades, reporting, integration recovery and controlled customization work can continue while the future-state decision remains open.
Can you maintain inherited Dexterity, VBA, .NET or SQL customizations?
The first step is to inventory source, build, deployment and data dependencies. Each customization can then be stabilized, documented, enhanced, replaced, redesigned or retired within an agreed risk boundary.
Do we have to migrate from GP to Business Central?
No. Business Central is one option, not an automatic conclusion. The decision should compare process fit, customization, integrations, reporting, data, controls, operating model and transition risk across viable targets.
Can the target be NetSuite or another ERP?
Yes, when the fit-gap evidence supports it. GP discovery, dependency analysis, data preparation, integration transition and reconciliation can be destination-neutral, with target-platform specialists engaged where required.
Can Salesforce and GP integrations be repaired or redesigned?
Yes. The work defines system ownership, business events, data contracts, API limits, validation, retries, duplicate handling, exception ownership and reconciliation before changing the interface.
Does naming a third-party product mean Aurosten is its partner?
No. Product names describe systems that may be encountered or evaluated. Partnership, reseller, certification or endorsement status is not implied.
Next step
Discuss your Dynamics GP environment
Describe the GP modules, customizations, integrations and immediate operating problem. The first conversation does not assume a migration destination.