QuickBooks to business central migration

Managing user permissions can be tricky when migrating to a new system. This guide will walk you through how to configure access controls in Business Central to protect data integrity.

When I assisted my client with their QuickBooks to business central migration, one key step was mapping user roles and permissions from their old system to the new one. With some planning and testing, we made the transition smooth and secure.

As an accounting platform, Business Central allows customized access restrictions, granular control of features, and data visibility. Whether you have five users or 50, following best practices here ensures a seamless shift for your organization.

Do Your Homework First

Before setting up permissions, take time to understand Business Central’s security concepts. Read through Microsoft’s documentation to grok core components like:

  • User roles
  • Role centers
  • Teams
  • Scope

Document your existing QB access structure and preferences. Identify key roles like Accountant, Sales Manager, and AP Clerk – think through their normal tasks.

Gather input from department heads on an ideal BC setup. Collaborate to determine appropriate access by role while limiting rights to protect sensitive information.

Map Roles & Restrictions

With foundations set, the real work begins! Here are the steps we followed:

  1. Create user roles that align to groups from legacy software:
  • Accountant
  • Sales Professional
  • Procurement Manager
  • Warehouse Clerk
  • Etc.
  1. Assign role centers that provide relevant views and functionality for each user role.
  2. Define scope to restrict record and table access as needed. Get granular with certain roles – e.g., AP can edit vendor data but not customers.
  3. Carefully review permissions for editing, creating & deleting transactions and records, and using key system functions.
  4. Consider the “Limited User” role, which blocks access to application setup for normal users.

Leverage built-in Business Central roles but customize as required – your needs are unique! Strike a balance between security and efficiency.

QuickBooks to business central migration

Test, Tweak, Repeat

Once the initial permission setup is complete, put it through its paces:

  • Have department heads and key users log in and exercise their roles.
  • Document any gaps or issues.
  • Make access adjustments based on feedback.
  • Test again until comfortable.

Resist the temptation for users to have broad “power user” access right away. Enforcing restrictions upfront is easier than trying to tighten down later.

As we dealt with permission pain points, I simply reminded my client: “Better to iron these out now rather than scramble after go-live!”

Audit & Optimize

Even after launch, access controls require care and feeding.

  • Review permissions quarterly to validate appropriateness.
  • Make tweaks as roles or needs shift.
  • Watch for new permission gaps based on user behavior or requests.
  • Coach employees to adopt better security practices.

By vigilantly optimizing and governing access, you confirm regulatory compliance and give stakeholders confidence in system integrity.

While restricting user rights takes some work, the long-term security payoff makes the effort worthwhile.

Following this process during your QuickBooks to business central migration ensures you maximize control over your new accounting platform. What challenges have you faced when mapping permissions to Business Central? Share your lessons learned.


Please enter your comment!
Please enter your name here