Sorry, I wasn't trying to say you were doing it wrong or anything.
------ Original Message ------
From: "Sterling Jacobson" <sterl...@avative.net>
To: "af@afmug.com" <af@afmug.com>
Sent: 1/10/2018 3:40:27 PM
Subject: Re: [AFMUG] Sonar Migration from Platypus
Sure, in my spare time I'll just create some DB scripts and then go
through every account to make sure it worked out and reload.
Oh wait, how is that saving me time and money?
It isn't.
I elected to take their import, do some brief overview to make sure
things were generally ok.
Then modify/update the ones that have problems.
Though that takes time, it's still less effort than starting from
scratch.
What I was told was it would be easy to migrate in a day or two and get
running.
So not the case.
-----Original Message-----
From: Af [mailto:af-boun...@afmug.com] On Behalf Of Adam Moffett
Sent: Wednesday, January 10, 2018 1:36 PM
To: af@afmug.com
Subject: Re: [AFMUG] Sonar Migration from Platypus
If I recall correctly, the Sonar documentation suggested using the API
to write a script to set everything up. I think the idea is you can
test your import script, then just blow away the Sonar instance and try
again if you have problems. Repeat until your script does everything
you want. Then when flag day comes you have a well tested process.
I know I heard that somewhere....if it wasn't in the docs it might have
been in one of the videos.
-Adam
------ Original Message ------
From: "Sterling Jacobson" <sterl...@avative.net>
To: "af@afmug.com" <af@afmug.com>
Sent: 1/10/2018 2:51:58 PM
Subject: [AFMUG] Sonar Migration from Platypus
So here is a current update on my months long progress moving from
Platypus to Sonar.
It's not automatic by any means.
Data import is taking a long time and its painful and costs a lot
extra.
I'm having to manually correct/add accounts to Sonar with rate group
changes, address validations etc.
They appear to be understaffed.
A lot of their system isn't theirs too, which is OK I guess, just
didn't realize that.
Import is a third party process if you don't want to do it yourself.
Actual payment site isn't them, you host it yourself or get a hosting
company, and have to maintain it yourself.
Paper statements are not directly them, you have to set up a third
party account and pay/manage them.
This is just a 'simple' import of billing function only.
I didn't even have any network information for any accounts, so I
shudder to think how that would have migrated.
Also I didn't really see them emphasizing the fact that their database
and Plat could get seriously out of synch if you are not careful.
I've had to manually suspend everything in Platypus to assure data
isn't out of sync with the new system until it comes online.
That means it's been days of people calling/contacting me trying to
pay
bills and I'm stuck in the middle.
Don't want to roll back since I've spent so many hours now on
migration.
Can't go forward yet because I'm still waiting on massive fixes to
rates on customers, and web site creation/setup for billing.
Let's just say I'm excited to get onboarding done and running, but I'm
also crying because it's not there yet and help is slow to come some
days.
