A Business Central payroll opportunity is emerging as Microsoft Partners prepare Dynamics GP customers for the move to the cloud. Payroll can give Partners a defined migration workstream, a specialized implementation service and a repeatable source of customer support revenue.
Microsoft will end Dynamics GP support on Dec. 31, 2029. Security updates, if needed, will remain available until April 30, 2031. The dates give Partners time to plan, although payroll cannot be left until the end of a migration. Tax calculations, employee records, benefits, project costs and general ledger postings all have to survive the transition.
PartnerTalks has previously examined the broader Business Central opportunity for GP Partners. Lee Parent of Sylogist says payroll gives the opportunity a clear delivery model.
GP migration puts payroll in scope
GP customers are accustomed to payroll operating inside their ERP. Business Central does not include a native North American payroll module, so Partners need to identify an extension and decide how payroll data will connect with finance, HR, projects and reporting.
Parent brings direct experience from both sides of the transition. He has worked in payroll for about 30 years, including implementation and product development across Canada and the United States.
“We actually were the team that built the original Great Plains payroll and then we shifted to Navision. For 30 years, we’ve been doing Navision payroll,” Parent told PartnerTalks.
Sylogist’s GP-to-BC migration guide recommends treating payroll and related HR data as a dedicated part of discovery, data preparation, validation, testing and change management.
For Partners, the Business Central payroll opportunity begins before configuration. Discovery has to identify pay rules, unions, multiple rates, tax jurisdictions, benefits, time systems, historical records and reporting requirements. Each dependency affects the migration plan and the customer’s ability to complete a reliable pay run after go-live.
Embedded payroll preserves the ERP experience
Parent said Payroll by Sylogist was designed within the Navision and Business Central environment. Employee cards, payroll journals and related records follow the same interface patterns customers already use for financial processes.
“There’s really no difference between accounts payable journal, payroll journal, customer cards, vendor cards, employee cards,” he said. “There’s that same look and feel throughout the entire thing.”
The Payroll by Sylogist product page says the extension connects with the general ledger, accounts payable, projects and vendors. It also supports federal, state and provincial tax updates, union agreements, benefits and varied pay structures.
Integration can reduce the number of handoffs between systems. It can also allow finance teams to use existing Business Central and Power BI reporting processes with payroll data.
Complexity creates room for specialization
Parent compared rigid payroll products to crossword puzzles. They work while every requirement fits a predetermined space. A new rule can force the customer into spreadsheets and manual work.
He compared Sylogist’s approach to a Scrabble board, where users can add a new word once they define the requirement.
“The more complex it is, the more effective we are and the more advantages we give,” Parent said.
Complex payroll environments create a stronger need for discovery, configuration, testing and ongoing support. They also make industry knowledge more valuable. A Partner familiar with construction, health care, education, government or multi-state employers can package payroll knowledge with its existing Business Central services.
The Business Central payroll opportunity can therefore extend beyond licence resale. It can include assessment, implementation, data migration, training, reporting, employee self-service and regulatory update support.
How the Business Central payroll opportunity becomes repeatable
Sylogist’s Partner model is central to Parent’s case. He said the company mentors Partners through initial setup and can train sales, implementation and development staff. The support can also extend into the first customer opportunity and implementation.
“As long as a partner is saying, ‘Yes, I want to do payroll,’ and as long as a partner can succeed once and then just replicate that success again and again and again, then they’re going to have an amazing time with our payroll product,” Parent said.
Repeatability depends on standardizing the work around the product. Partners need a discovery checklist, a migration map, a test-payroll plan, a training sequence, and a post-go-live support process. Industry-specific templates can reduce delivery risk across later projects.
Payroll data supports wider business decisions
“Paying people is a side effect of payroll,” Parent said. “What you really want is to empower the company to be able to take that payroll information and help it make decisions to succeed.”
Payroll data can inform labour costing, project profitability, staffing, benefits and financial forecasts. Keeping it inside the ERP gives Partners another way to connect implementation work with the customer’s operating decisions.
The GP deadline creates some urgency, but he Business Central payroll opportunity gives Partners a service line they can begin building before customers reach the migration queue.
