OK - If you have an Open GI problem or don't know your ReportNet from your Calc Code, then post your questions here. Someone, somewhere will have the answer and you may get a faster response than a support call!
Open GI launched their new platform solution "Mobius" at BIBA 2018
This Forum is for existing Open GI "Core" customers and all new prospects to discuss the new options now available and their experiences of this new technology offering. If you have seen it, then share your thoughts and comments here. If you haven't, why not get a demo and see what the future will bring. Bookmark this page for an unbiased and transparent view as part of your Due Diligence - before you jump in feet first! All comments welcome
There will be issues whichever way - so you need to pick the right way for you at get it right first time.
In short - and from experience on both sides - I'd say transfer now to your server, as separate branches. This may involve some logistics for connectivity (I don't know your set-up) but on the face of it - is better than running multiple servers and multiple business processes. You'll thank yourself in the long run
Moving / migrating / transferring / consolidating to one branch - on the same server - is far, far easier to manage once the data is on one platform. Trust me on this.
Sorry Sandra - Are you planning to merge the branches on THEIR system - or merge and migrate to your server?
The first is as everyone has said above - the latter is potentially a whole new world of complexity - x 10!
I’ve done this many years ago. If you merge branches into one, bear in mind client/policy references which are already taken on the target branch will get a new number. Therefore, if you have direct debit with a finance provider such as Premium Credit, you may have to provide them with a cross reference list.
We also got OGI to stamp the BPY notes with the original ref.
Thanks for your reply John - Yes it is OGI to OGI (broker acquisition and they have 2 separate branches whereas we have only one) and we are aware of the complexities in respect of the settings etc - may well be better to keep the two extra branches separate then drip feed onto one branch at renewal maybe?
We realise policy modules etc will differ and just wondered if anyone had migrated, what actually happens if two clients have the same reference number?
Will certainly keep you updated
Big question - and lots to consider. You haven't said, but I presume this is to do with an OGI to OGI transfer, with branches already on the same server? If so - and to help kick this off, top 5 tips below from me:
Specification - Make sure you have a spec of what will - and what wont - be transferred
Settings - Check that all your settings are the same. Many are branch independent and you really need to check all of these for future use. This includes source codes, exec codes, Database Reports, User Access authorities, Broker Record / Prospect record settings, Regulation Module options, Document / letter templates to name a few from a long long list
Prospects - Do you use APM / Prospects - and what will happen with these records
Accounts and EDI - If it's OGI>OGI then EDI should be OK, but you do need to have a plan for the accounts. For both, will the old branches be in run-off or transferred en-bloc / big-bang? If Run-off - how are you maintaining both sets of data?
Why? - Revisit why are you doing this anyway - quite often it's not the only solution - and I'd be interested more in what you are trying to achieve and why you think branch consolidation is the answer
I'm sure Open GI will have already asked all the above questions - and more - to get to the right solution for your business. But always worth taking advice on a big change Hopefully others will have input as well
Good luck and let us know how you get on!