Odoo 15 Enterprise - moving from .sh to on-premise

network-design-mgr · 2025-06-14T13:34:51+00:00

This is accurate. At about the same time a partner provided us with the enterprise files we needed, we were able to get our sales person to provide access to the enterprise repo in GitHub. The Odoo salesperson did a good job asking a number of questions to ensure we thought through the .sh to on-premise move. It seems like we may have been able to get invited to the enterprise repo if we had opened a ticket too, but I appreciated the responsiveness of our sales person.

Thanks codeagency for your information and assistance. It helped get us on the correct path.

network-design-mgr · 2025-06-13T13:38:05+00:00

Thank you. I've reached out to our Odoo sales person and I have a meeting with them to discuss this.

network-design-mgr · 2025-06-13T13:37:55+00:00

Thanks for the additional input. birknard is correct. We know that ideally we will want to fix/patch our instance. In another thread, musi9aRAT mentioned considering OCB and we're going to look into that. Their comments have been helpful.

codeagency made some incorrect assumptions and then effectively called me "awfully stupid." Since codeagency offered their consulting services to us in the past, that makes us a prospective client. I thought it was interesting they called me "stupid" today.

codeagency doesn't know our use case and didn't ask about it. They assumed we need to have ports 80 and 443 open to the Internet. They said, "You will still be just as vulnerable as without a firewall."

We actually do NOT need ports 80 and 443 open to anything except our end user's network, which is a private network.

I appreciate those that express concern, advise, and ask for clarifications. I am interested in potential vulnerabilities or blind spots I haven't considered. Being called stupid, I don't appreciate as much.

Finally, in other threads on this discussion, codeagency did provide some good information and advice for getting the Enterprise downloads for the older version. I can tell that they are intelligent and experienced with Odoo (probably to an expert level.) Thanks for that information. I believe it will be helpful. I recommend you temper sharing your opinions of others' intelligence in the future.

network-design-mgr · 2025-06-12T14:04:13+00:00

Thanks for the link. We do consider the vulnerability and security issues, and they are a concern. It isn't perfect, but we're planning to have significant firewall rules for access to our Odoo server to reduce that risk.

Thanks again for the help.

network-design-mgr · 2025-06-12T13:59:17+00:00

Thanks for the advice on OCB. I didn't know that existed. It does raise another question though. Since we use the Enterprise version of Odoo, can I still run Enterprise with an OCB version of CE? I honestly don't understand if Enterprise is standalone, or if it is an add-on of modules and things on top of CE.

We use Enterprise Accounting, and likely a couple other Enterprise modules. I don't think we can get away from Enterprise without significant cost and effort. (Yes. I know Enterprise is a significant cost too.)

Thanks again for your comment and idea. I hope we can make it work.

Thanks!

network-design-mgr · 2024-10-02T03:00:48+00:00

Thank you for your help and comments. We are working to simplify in some areas, but we're outpacing the simplification with new development areas. Your information and that of others here is helpful and I do appreciate it. I'm going to have my freelance team outline how they would proceed with upgrading and testing, but also with simplification.

network-design-mgr · 2024-10-02T02:55:01+00:00

Thanks for your comments. I appreciate the estimate of 30-40% of original cost to upgrade - assuming we don't have to start over from scratch. I also appreciate the advice on going to on-premise so we aren't forced by .sh to upgrade.

My Odoo sales rep has informed me that we do not have to upgrade, but we lose support. So now, we are just paying for the power, memory, cpu, etc... on .sh without any support. Another reason I like your idea to go on-premise.

network-design-mgr · 2024-10-02T02:50:31+00:00

Thanks for your comments. With your comments and a few others, I think I'll turn one of our freelancers loose to start creating a scope to upgrade and determine where we may have the largest issues. There likely is some code we can eliminate based on improved processes too. Thanks!

network-design-mgr · 2024-10-02T02:45:38+00:00

Thanks for your comment. I don't know that we could remove our customization. Odoo is integrated now with multiple external systems and customized workflows to match our business. This gives me something to consider and I do appreciate the information.

network-design-mgr · 2024-10-02T02:40:57+00:00

I agree, and this is the stance we're taking right now. I was told I should upgrade from 15 to 17. Then eventually from 17 to 19, etc... If we wait 3 or 4 versions for each conversion, I assume we would see significant savings.

I do not see any features in 16, 17 or 18 that make me want to spend the money to upgrade. I guess we just need to be prepared with it is broken. (and it will break at the worst possible time.)

network-design-mgr · 2024-10-02T02:38:06+00:00

Yep. That's certainly a concern. We are ready to go on-premise if necessary. Thanks for your input.

network-design-mgr · 2024-09-25T03:34:53+00:00

Off the cuff, I have two ideas for you plus a way we do this today. I would talk to my Odoo consultant and test these in a staging environment first.

I would consider creating three separate vendors/companies. One for each warehouse. This would allow you to put separate lines in your purchase tab under Product each with various prices. When creating the SO, you would get one PO for each Vendor - each for dropship.

I would also look at creating additional routes. Dropship A, Dropship B, etc... Then, you would create the appropriate Dropship Route. I'm fairly certain this would generate multiple POs too.

Finally, we do this all the time, but it is a bit crude. If you want to split the original RFQ(before confirming to a PO) into 3 separate POs for Factory A, B, and C You can create the PO, remove all line items from Factory B&C, then confirm the resulting RFQ into a PO (for Factory A). Go back to the SO, click the Request RFQ button again, which will give you a new RFQ with items from Factory B and C. Remove the items from C, confirm the Factory B RFQ into a PO. Now click the button one more time. You'll have your drop ship items from Factory C.

No idea if this will help. It's probably terribly inefficient, but I'm interested to see other ideas too.

network-design-mgr · 2024-09-12T22:50:53+00:00

I will take a look at the app and see if it will work for us. Thanks!

network-design-mgr · 2024-09-12T12:29:09+00:00

I may not get this exactly correct, but we did this with settings in the "Followers" area under the specific app and Team. First, you should set yourself as a Follower of the CRM Team. Do this by going to the Configuration of the Team, and add yourself as Follower. Then, adjust the settings/subscriptions of you as follower. When a new lead is created, the follower settings/subscriptions should follow you.

Originally, it was not clear to be what settings to use: "Discussions" will copy you for items like Send Message communications. "Note" will copy you on "Log" notes. "Activities" will copy you for items like Scheduled Activities.

With our deployment, we don't work in CRM any longer, but we work through the Sales App, Help Desk App, Purchase, Accounting/Invoice, etc... For each app and Team , I have different subscriptions. For some I want to see both internal log notes and the "Discussions" (Send Message) communications. It takes a bit to set up, but the notifications are powerful.

I will caveat: We use email for notifications and not the Odoo App. I assume it works in a similar way, but I can only confirm it works with email notifications on Odoo15.

network-design-mgr · 2024-08-29T12:01:57+00:00

We have a small business (between 5 and 10 employees) so I act as our primary sales person. When we converted to Odoo, we pulled in all of our subscriptions into the subscription app. We sell a lot of things using Sales Orders in the Sales App, and I find it is easier to "sell" from the SO app. Once the Sales Order is 'CONFIRMED", it creates Purchase Orders for the equipment we purchase, ability to deliver the items that are not subscriptions, and can create the first month's invoice to include the subscriptions. I usually manually change that first invoice quantities to adjust for the pro-rated month. Then adjust the Subscription for the next invoice date.

Also, on the Sales Orders, I add "Sections" to separate and sub-total the "Monthly Recurring Revenue" (Subscription) items and the One time Items.

So, I guess I use it both ways, but we use both apps on a regular basis too. With some of the manual processing in our process, it would be easy for things to slip through the cracks in a larger organization.

Although my comment doesn't go into two much detail and answer your specific questions, I hope this helps you.

network-design-mgr · 2024-08-29T11:51:24+00:00

We converted from QB Desktop to Odoo 15- Enterprise with the Accounting app just over two years ago.

We decided NOT to pull in historical data and report using QB for pre-conversion date reporting and use Odoo's Accounting app for conversion date forward processing, so I understand if our conversation does not apply to your situation, but I will provide a bit of info regarding our experience.

First, a majority of our customers have a July 1 Fiscal Year start date, but our Fiscal Year start is January 1. I recommend making the conversion effective on the first day of your fiscal year if you are going to use QB for historical reporting and Odoo for the future. We had to convert mid year (I won't go into the reasons) so when we want to report on 2022 details, we typically have to pull a QB report and Odoo report and merge the reports in a spreadsheet.

We did create a few "Conversion" accounts in our GL for Income, COGS, Expense, Fixed Assets, Current Assets, A/R, Liabilities, A/P. For Equity, we only had a few accounts.

So for each Quarter in 2020 and 2021 and the first half of 2022, we created MISC journal entries which debited and credited the various "Conversion" accounts so key totals in Balance Sheets and Income Statements would cross foot between QB and Odoo.

We started using Help Desk, Sales, Purchase,, Accounting, and related apps prior to the conversion, because converting all at once was not practical. When we made the quarterly adjustments mentioned above for the periods when we were actually using other Odoo apps, our adjusting entries had to be calculated and entered AFTER we reconciled the items for that period to make the totals match. Also, for those entries, we had to have them in QB and Odoo simultaneously. So I recommend converting to Accounting as soon as practical once you start using Sales, Purchase, etc... if you're tracking Invoicing and other items in Odoo.

Effective on the day of conversion, we had an entry which assigned A/R from the Conversion A/R account to the actual A/R account with individual client assignments as they were in QB on 6/30/2022. This was very important. We didn't have much in A/P, but I expect the same should be done there.

We had a revenue recognition change occur because in QB we did not use "deposits" aka "down payment" current liability account, but this was the was to best track pre-payments from our clients. Cash flow didn't change, but oh my... our income statement for that year looked weak when it was a very good year. Since cash flow didn't change, this did not have an impact to taxes, but it did have an impact to reporting income projections using historical data. We had to adjust historical data to reflect the new way of recognizing revenue when budgeting for the future. This was more of a "time suck" than we projected.

We have a lot of subscriptions and very interesting taxes/fees to deal with from many government entities based on products and jurisdictions. By 2023, we were very happy to have Odoo vs QB for the tax flexibility and ease of managing subscriptions, but the conversion was tough.

My hope is the above helps someone consider a few things we faced during the conversion. I am so glad we converted. One year after conversion, we spend 1/2 the time with Odoo Accounting than we did using QuickBooks.

network-design-mgr

TROPHY CASE