Fixed-price dynamics gp migration assessment in 2–4 weeks. Per-company DB inventory, Dexterity / Modifier / VBA catalogue, ISV add-on inventory, SmartList Builder complexity rating, sized 12–18 week migration plan with risk register. Defensible artefact your board can act on.
Most GP-to-Fusion projects slip because the scoping phase missed Dexterity dictionaries, ISV data footprints or SmartList complexity. A proper assessment surfaces all of it before contracts are signed.
The traditional GP-to-Fusion scoping pattern is built around the consultant economic model: a few discovery workshops, a high-level scope, a time-and-materials contract that protects the consulting firm from the things the workshops missed. The customer signs up for a project they believe will be 12 months and USD 800K; they end up at 22 months and USD 2.4M because Dexterity dictionaries nobody mentioned in the workshops drove critical post logic, because a Mekorma add-on the AP team relies on requires a Fusion redesign nobody scoped, because 400 SmartList Builder queries finance refuses to lose got discovered in month 6.
Syntra ETL's dynamics gp migration assessment inverts the model. Week 1: automated discovery engine connects to SQL Server (read-only), enumerates every company DB from DYNAMICS.SY01500, walks every customisation table (Modifier resources, VBA project metadata, SmartList Builder definitions, Dexterity dictionary inventories, active ISV product schemas), produces a complete inventory in hours. Weeks 2–4: functional workshops with finance, AP, AR and ops to classify the discovery findings by business value and Fusion replacement difficulty.
The output is five concrete deliverables: per-company DB inventory, Dexterity/Modifier/VBA catalogue, ISV add-on catalogue, SmartList Builder complexity rating, sized migration plan with 12–18 week timeline, fixed-price budget range, risk register and explicit phasing recommendation. The assessment fee is credited against the full project if you proceed within 90 days — but even if you don't, you walk away with a defensible internal artefact your board can act on or any other consulting firm can execute against.
The dimensions consultant-led scoping routinely under-estimates — quantified with hard evidence from the source GP installation.
GP's one-DB-per-company pattern is the single most underestimated complexity driver. The assessment counts every active DB and surfaces account framework variation explicitly.
Segment count, segment width and segment order can vary across company DBs in the same GP install. Assessment surfaces every variation with a recommended Fusion COA mapping.
Every .dic with the custom forms, logic and tables it carries. Classified retire / DFF / AMX / OTBI / custom-dev. Typical: 30–50% retireable.
Mekorma, Greenshades, Integrity Data, Rockton, Binary Stream, eOne, Encore. Each with data footprint, Fusion-equivalent recommendation and sunset sequencing.
Every query enumerated from SmartList Builder metadata. Rated by complexity and business value. Tiered replacement plan with rebuild sequencing.
Fiscal-year depth per table per company. Determines whether full history loads to Fusion or routes to long-term GP cloud archive.
A repeatable, governed assessment workflow with explicit gates. Single-company SMB: 2 weeks. Mid-market: 3 weeks. Multi-entity 12+ companies: 4 weeks.
Kickoff with finance / AP / AR / ops / IT. Read-only SQL Server credentials provisioned. Optional eConnect or Web Services for GP credentials provisioned if security policy requires non-SQL access path.
Discovery engine crawls every company DB enumerated from DYNAMICS.SY01500. Customisation tables walked. ISV registry interrogated. SmartList Builder metadata extracted. Row counts and storage sizes captured. Output: raw inventory ready for functional review.
Functional workshops with finance, AP, AR, ops, payroll, IT to classify every discovery finding by business value, Fusion replacement difficulty, and retirement candidacy. Account framework cross-walks drafted. ISV decommission sequencing drafted. SmartList rebuild priorities drafted.
Risk register built (Dexterity-dependent business logic with no Fusion equivalent, ISV vendors with announced GP end-of-support, multi-company account framework collision, SmartList complexity tail). Sized migration plan drafted with 12–18 week timeline and fixed-price budget range.
For multi-entity rollouts: explicit phasing recommendation (which BUs go first, sequencing rationale, parallel-run windows, hybrid intermediate states). For hybrid plans: which modules stay on GP, integration bridges, decommission timelines for retired modules.
Final assessment package delivered: 5 deliverables (DB inventory, Dexterity/VBA catalogue, ISV catalogue, SmartList rating, sized plan with risk register). Review session with sponsors. Sign-off gate. Assessment fee credits against project fee if commit within 90 days.
The five concrete deliverables — defensible artefacts, not consultant slide decks.
Excel + PDF: every company DB from SY01500, row counts per active and historical table per company, fiscal-year depth, storage size, account framework variation. Defensible scope baseline.
Every .dic dictionary, every Modifier-altered window, every VBA project enumerated with business purpose classification and Fusion-equivalent recommendation. The 30–50% retireable items explicitly flagged.
Every active ISV product with data footprint, current vendor support status (many ISVs have announced GP end-of-support), Fusion-equivalent recommendation and sequenced decommission plan.
Every active SmartList Builder query rated by complexity and business value. Tiered rebuild plan: critical operational pre-go-live, daily operational first 90 days post, ad-hoc on demand. 30–50% retireable count.
12–18 week timeline (mid-market scope) with phase gates, fixed-price budget range, risk register, phasing recommendation for multi-entity rollouts and hybrid options. Board-ready document.
The deliverables stand on their own. If you decide to use a different consulting firm or do the migration yourself, the artefacts remain defensible inputs to any executor.
A dynamics gp migration assessment from Syntra ETL produces five concrete deliverables: (1) Per-company DB inventory — every active company database enumerated from DYNAMICS.SY01500 with row counts per active and historical table, fiscal-year depth, storage size, account framework variation; (2) Dexterity dictionary inventory — every active .dic file in the source GP installation with the custom forms, custom logic and custom tables it carries, classified by business purpose; (3) ISV add-on catalogue — every active partner add-on (Mekorma, Greenshades, Integrity Data, Rockton, Encore, etc.) with its data footprint and Fusion-equivalent recommendation; (4) SmartList Builder complexity rating — every active SmartList Builder query rated by business value and Fusion replacement difficulty; (5) Sized migration plan — 12–18 week timeline, fixed-price budget range, risk register and the explicit phasing recommendation for multi-entity rollouts.
Two to four weeks end-to-end depending on installation complexity. Single-company SMB with no ISV add-ons and minimal Dexterity customisation: 2 weeks. Mid-market 4–6 company DB installation with active Mekorma, Greenshades and a few hundred SmartList Builder queries: 3 weeks. Multi-entity 12+ company installation with active Dexterity customisations, multiple ISV add-ons and a decade of accumulated SmartList complexity: 4 weeks. Week 1 is always automated discovery — connecting the discovery engine to SQL Server and letting it crawl. Weeks 2–4 are functional review, finance/AP/AR workshops to classify findings, and sized plan production.
A fixed-price assessment runs USD 12K–35K depending on installation complexity. Single-company SMB: USD 12K. Mid-market 4–6 company: USD 20K. Multi-entity 12+ company with heavy Dexterity / ISV / SmartList footprint: USD 30K–35K. The assessment fee is credited against the full migration project fee if you proceed within 90 days. The output stands on its own — even if you decide not to proceed with Syntra ETL, you walk away with a defensible internal artefact: per-company inventory, Dexterity/ISV/SmartList catalogues, sized plan with risk register that any other consulting firm can execute against.
GP's pattern of one SQL Server database per company is the single most underestimated dimension of a GP-to-Fusion project. The assessment engine starts at DYNAMICS.SY01500 to enumerate every active company DB (TWO, FAB1, customer-specific codes), then walks each company DB in parallel to capture row counts per table, fiscal-year depth, account framework variation (segment count, segment width, segment order can vary across company DBs even in the same GP install), vendor and customer master overlap across companies (de-duplication candidates), and inter-company transaction patterns. The output explicitly calls out the per-company variation so finance and IT leadership can scope the migration honestly — single-company is one project, 12-company multi-entity is genuinely a different project.
Discovery walks every active Dexterity dictionary (.dic file in the GP installation directory and registered in DYNAMICS.SY00100), enumerates the custom forms, custom logic and custom tables each dictionary carries, identifies every Modifier-altered window via the SY00100 Modifier resource metadata, walks every VBA project via the SY01401 VBA project metadata, and classifies each customisation by business purpose. The output rates each customisation: 'Retire' (redundant under Fusion's native capability — typically 30–50% of GP customisations), 'Replace with Fusion DFF / value-set' (data-collection customisations), 'Replace with Fusion AMX' (approval-flow customisations), 'Replace with OTBI / BI Publisher' (reporting customisations), 'Custom Fusion development required' (the small minority that needs explicit redesign).
Yes — and the ISV catalogue is one of the most under-appreciated assessment outputs. Discovery enumerates every active ISV product registered in the GP installation: Mekorma (AP payments, check printing, MICR), Greenshades (payroll/tax filings, ACA reporting), Integrity Data (payroll add-ons), Rockton Software (Auditor, Toolbox, SmartFill, others), Encore Business Solutions (various financial add-ons), Binary Stream (multi-entity management, property management), eOne (SmartConnect, SmartPost, Extender), and any other registered partner product. Each ISV gets a Fusion-equivalent recommendation, a data-footprint assessment (how much partner-specific data sits in GP custom tables) and a sequenced sunset plan — many ISV vendors have already announced GP end-of-support, so the migration plan has to land before their support ends.
SmartList Builder is the de facto reporting layer in most GP installations — finance, AP, AR and ops teams have built hundreds of custom queries over a decade of use. Assessment walks the SmartList Builder metadata tables (the SmartList_Builder schema in DYNAMICS) to enumerate every active query, classify by complexity (number of joined tables, calculated fields, parameter prompts, output formatting) and business value (daily operational vs monthly close vs annual audit vs one-off). The output is a tiered replacement plan: critical operational queries rebuilt as OTBI analyses or BI Publisher reports before go-live, daily operational queries rebuilt in the first 90 days post-go-live, ad-hoc queries available on demand. Typical assessment finding: 30–50% of accumulated SmartLists can be retired (duplicates, abandoned, or redundant under Fusion native reporting).
Yes. Many SMB and mid-market customers run a hybrid pattern: financials migrate to Fusion, payroll stays on Greenshades or a specialist payroll provider, project accounting stays on a vertical partner add-on, or one less-mature business unit stays on GP for another 12 months while the larger units cut to Fusion. The assessment explicitly handles hybrid scope: which modules go, which stay, which integrations bridge the two systems (real-time vs batch, eConnect vs Web Services vs Fusion REST), and what the phased decommission timeline looks like for the modules and ISV add-ons being retired. The dynamics gp migration assessment output is a realistic plan, not an all-or-nothing recommendation.
Fixed-price 2–4 week assessment. Five concrete deliverables. Defensible artefacts. Fee credited against your full migration if you proceed within 90 days — and yours to keep either way.