We recently had a meeting to discuss how third-party integrations (those add-ons your clients use) are shaping up for the switch to 64-bit Sage 100. Why is this important? Well, soon Sage may only issue Sage 100 upgrades at 64-bit.
This means that eventually, you’ll need to upgrade to 64-bit Sage 100, and that means making sure their integrations are compatible. We’re already tracking which integrations are ready for 64-bit, which ones aren’t, and which ones are still a question mark. The good news is that most popular integrations claim to be 64-bit ready. We even have a document that lists them!
But there’s a catch…
Even though an integration might work with 64-bit Sage 100, you might still need to reinstall it after upgrading. Here’s why:
- You can’t run 32-bit and 64-bit Sage 100 on the same machine. So, some of you might be thinking, “I’ll just upgrade my system to 32-bit first, then use the handy conversion tool to switch them to 64-bit.” Sounds easy, right?
- Not so fast! Some integrations need a fresh install after that conversion, even if they’re technically 64-bit compatible. And reinstalling one integration can trigger a domino effect, requiring you to reinstall all of them. Ouch! This can be a simple process or a major headache (and expense) depending on the integration.
What should you do?
- Talk to your ISVs. If you’re planning to use the 32-bit to 64-bit conversion tool, check with every integration vendor to see if their product needs to be reinstalled.
- Consider a server upgrade. In some cases, it might be easier to implement a new server to avoid compatibility headaches with Sage 100 32-bit and 64-bit on the same server ( which reported does not work ).
Key takeaway: 64-bit Sage 100 is the future. Start preparing now to ensure a smooth transition for your clients. Don’t get caught off guard by these integration quirks!
