Announcements
How scalable is BC? If I have a 30 user GP client with 100GB of data collected over 25 years can BC handle that? They also spend all day generating purchase orders off sales orders, can BC handle to GP SOP to POP commitment process?
Richard, this may be a good question to ask of the D365 BC forum here > community.dynamics.com/.../dynamics-365-business-central-forum
Support engineers from that team monitor that forum the same as we do this forum, so you may be able to get an answer from one of them, as well as anyone in this forum's community that has experience on the BC side as well.
Thanks
Derek, I have posted this question in both forums to get everyone's opinion. I also have a question over there about why I am not able to setup any GP to BC migrations. I am hoping someone has an answer as I am stopped from going any further. If you search for other BC queries from me you will see my issue.
Business Central's scalability is the same as Dynamics GP - From 1 to hundreds of users. We have clients of both GP and BC with a terabyte or more of data.
Business Central generates purchase orders off of sales orders similarly to Dynamics GP. There is an advantage to BC, however, in that since BC is fully customizable, you can more easily automate POP-SOP processes through development. (GP is meant to work more out of the box, whereas BC is meant to be easily customizable.)
Regarding migrating from GP to BC, there are a lot of caveats with that process. I spoke on this topic at Summit. Here is a link to a video describing the pros and cons of the various migration scenarios: https://youtu.be/VZykyRe5Jis
My issue is of a technical nature. Have you ever run into this?
Setup Cloud Migration -> Accept Privacy Warning -> Select Dynamics GP as the product -> Enter connection string and Integration Runtime Name -> It will say “Working on it” and then I sit and wait and get the message “Failed to enable your replication” and looking through the logs there are no errors but these warnings.
I have checked all of these:
The Self-Hosted Integration Runtime Diagnostics tests the connection successfully
The SQL compatibility level is SQL 2019(150)
The provided connection string is correct.
I checked with one of our engineers that has done a number of GP-BC migrations, and he believes that the SQL Connection string is incorrect or permissions on the account being used in the SQL connection string are incorrect\insufficient. You need dbowner permissions; sa is the safest bet.
Your video was excellent. Thank you.
Here is the connection string.
Server=MyWorkstation;Database=DYNAMICS;User Id=sa;Password=MyPassword;
MyWorkstation is a W10 Professional Workstation
SQL is SQL 2019
sa is the user
password is the dummy password on this computer for SQL.
GP 18.2 runs just fine and I log into GP with these same credentials.
My thinking now is to try on an image of a server. The server must be at least W2012 R2 and SQL has to be at least 2016, correct?
OK, I have now tried this from two computers and it fails both times. Here is my connection string. Is there anything wrong with this?
Server=myServer;Database=myDataBase;User Id=sa;Password=myPassword;
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Giorgio Bonacorsi 676
Abhilash Warrier 635 Super User 2026 Season 1
André Arnaud de Cal... 605 Super User 2026 Season 1
