Hi Pat,
We are transitioning from HTE (Select/NaviLine) to Tyler Munis. We're about
half way through core financials.
When implementing new financials, it's likely a new a chart of accounts will be
created. The replacement software will have a different coding scheme. Most
will make an effort to make the new chart similar to the old. For example, the
same fund numbers, department numbers and potentially similar object codes. A
new chart is an opportunity to clean up some of the legacy strangeness in the
current chart (if any). The new software's chart coding scheme will support
desirable features in the software that finance will want to take advantage of.
The point is, I would plan on a fair amount of change in the chart of accounts.
Change in the chart will severely limit your capability to convert historical
data. For example it's not impossible, but quite difficult to convert
transaction detail after you make changes to the chart. So much so that ERP
companies like Tyler will not convert detail without a fight and $$$. Also,
the farther back you go the less desirable converting data becomes. Why?
Because accounts come and go over time. The number of
no-longer-existing-accounts (even entire account numbering schemes) increases
the farther back you go. You'll end up creating accounts in the new chart that
are unnecessary or even not applicable to the new chart. Essentially creating
garbage.
For core accounting we are converting only budget and actual summaries, and
beginning and ending balance data for the last three years including the
current. So fiscals '15, '16 and '17. We go live the first day of fiscal '18
(July 1, 2017). We in IT are responsible for extracting the appropriate data
from HTE. It's not terribly difficult. Supporting data like fixed assets,
vendor files and the like are relatively straight forward. Though a fair
amount of manual cleanup may be necessary depending on the requirements of the
destination software. Our finance was did that work. They wanted to do some
house cleaning anyway. The remainder of our HTE accounting data going back to
1999 will be exported and converted to MSSQL Server tables for posterity and
curiosity. We'll be in no hurry to complete that work while the 400 still hums
along.
The conversion we're not looking forward to is HR/Payroll. We know there's are
real challenges and a good deal of work hiding there.
Best!
Joe Sadony
Director, Deschutes County Information Technology Dept.
(541) 388-6530
Joe.Sadony@xxxxxxxxxxxxx<mailto:Joe.Sadony@xxxxxxxxxxxxx>
http://www.deschutes.org
From: oagitm-bounce@xxxxxxxxxxxxx [mailto:oagitm-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Hartley, Pat
Sent: Tuesday, January 10, 2017 10:21 AM
To: oagitm@xxxxxxxxxxxxx
Subject: [oagitm] SunGard & NaviLine Users
Howdy folks and Happy New Year!
I am writing to do a bit of a survey as to who among us is using (or used in
the past) the SunGard NaviLine solution.
If you have, would you mind telling me:
- Have you recently transitioned to another ERP solution or are you
planning to do so?
- If you have transitioned or plan to; How did you approach the
extraction of legacy data? For example, did you engage with SunGard/HTE,
utilize internal IT resources, or contract with a third party?
- Was this an effective approach? What would you do differently to
improve the process and the results?
Thank you guys very much. I appreciate your time!
~Pat
Pat Hartley, IT Director | City of Gresham
Skype<im:%3csip:pat.hartley@xxxxxxxxxxxxxxxxx%3e> |
Pat.Hartley@xxxxxxxxxxxxxxxxx<mailto:Pat.Hartley@xxxxxxxxxxxxxxxxx> |
503.618.2520
1333 N.W. Eastman Parkway | Gresham, OR 97030-3813
[banner2small]<http://greshamoregon.gov/>