Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
FTKing
Starting Member
5 Posts |
 Posted - 2011-09-28 : 10:59:28
|
| Let me preface this by saying I know almost nothing about databases. Our company is purchasing new ERP software, migrating from an old FoxPro based Epicor Vista 4x to a new program which uses MS SQL. They keep telling me that we're going to be able to migrate almost all of our data, but we won't be able to keep the transaction data. For example, we can keep our list of customers and their addresses and phone numbers, but we won't be able to see the list of what they bought and when they bought it and at what price it was bought. This is going to create a huge inconvenience because everyone here is going to have to have access to both the old server and the new server. However, one guy I talked to said he had someone come in and migrate their data, and he didn't remember losing transactions.Is it possible that the new company is wrong and I will be able to keep this data, or is this most likely right?Thank you! |
|
|
Ifor
Aged Yak Warrior
700 Posts |
Posted - 2011-09-28 : 11:49:13
|
| I know nothing about the products you mentioned, but in general terms converting transactional accounting data can be very time consuming and expensive.Also, if the chart of accounts is significantly different in the new system, the converted data may be of doubtful quality.I suspect a business decision has been made not to convert transactional data for some, or all, of the above reasons.You should really contact the Project Manager, who is implementing the new system, to find out why transactions are not being converted. |
 |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-09-28 : 12:03:27
|
| There is absolutely no reason for leaving the transaction data behind. Either they don't know what they're doing or the implementation is VERY poor.VFP to MSSQL is not a difficult transition as far as migrating data. |
|
|
|
Ifor
Aged Yak Warrior
700 Posts |
Posted - 2011-09-28 : 12:22:35
|
quote:
Originally posted by russell
There is absolutely no reason for leaving the transaction data behind. Either they don't know what they're doing or the implementation is VERY poor.VFP to MSSQL is not a difficult transition as far as migrating data.
Moving data from VFP to MSSQL is not difficult but the controls in the source and destination systems may be very different. Also, when accountants want a new system it usually indicates a change in company structure and/or statuary reporting requirements which require a new chart of accounts.The last time I had any involvement in a new accounting system, only the balances and the open transactions were migrated. Other relevant transactions were just dumped into a separate reporting database so as to not clutter up the new system. |
|
|
|
FTKing
Starting Member
5 Posts |
Posted - 2011-09-28 : 12:56:56
|
| Ifor and russel thank you for your response. I guess I always just thought that this information would be stored in a database like any other info. e.g. field for amount purchased, field for date purchased, etc. I have talked to the project manager, but we work in a relatively small company and the company we are purchasing the new software from told him that it wasnt possible to transfer the data, so he is just going with this notion. If it would be possible for us to hire an SQL guy to come in for a few days and do this, it would be great.I do know that we don't use the system for most accounting purposes. We do enter quotes, order prices, and invoices in the system, but don't use it for our financial acct. We have separate accounting software, and we aren't undergoing a change this area. We are updating soley because our current ERP system prevents us from upgrading the rest of our hardware and software because the newest OS it supports is Win XP.If you guys think it might be possible to hire an outside person to transfer this data, I can look into it.Thank you |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-09-28 : 13:26:30
|
quote:
Originally posted by Ifor
Moving data from VFP to MSSQL is not difficult but the controls in the source and destination systems may be very different.
Sure, but that is no reason not to do the data mapping.quote:
Also, when accountants want a new system it usually indicates a change in company structure and/or statuary reporting requirements which require a new chart of accounts.
Sometimes, sometimes not. If the legacy system uses FoxPro, it's not difficult to imagine that they simply outgrew it, or are upgrading to supported systems -- as is the stated case with the OP. Either way, you don't just decide "It's too hard, let's leave it behind." In fact, the VERY FIRST part of this type of project is to map the data structures and document it. Not doing so is a recipe for disaster, or at least problems down the road.quote:
The last time I had any involvement in a new accounting system, only the balances and the open transactions were migrated. Other relevant transactions were just dumped into a separate reporting database so as to not clutter up the new system.
If they're relevant, they need to be migrated. If it's "clutter" there's a problem with the new system design/specs.In short, any data that matters should be migrated.If the vendor tells you it can't be, they're wrong. We can't tell from here if it should be, but if you suspect it should, dollars to donuts says you're right and it would be worth hiring a consultant who understands the technical aspects to evaluate it for you. That said, the vendor performing the upgrade is supposed to be an expert, and I'd have some very pointed questions for them. |
|
|
|
FTKing
Starting Member
5 Posts |
Posted - 2011-09-28 : 15:02:55
|
| russell, From what you've written it sounds like it is at least possible to do this migration, so I will see what I can do about contacting a consultant to give us an opinion. This data would be very helpful because we have many customers that order from us only once every year or couple of years and it is critical that we have access to the order history so that we correctly price the new order. If we don't migrate this data, a lot of people here will be running back and forth from their workstation to legacy workstations in order to write down or e-mail old data, which would just be a drain on productivity.I do appreciate your help and I will give my opinion to our project manager. I agree that the vendor should probably have better answers for us, but our situation is a bit different than their typical customer. I have found the contact information for one of their software engineers and in addition to contacting a consultant, I'll try that route to see what they have to say. Thanks |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-09-28 : 20:42:43
|
| As questions arise do post back.In my opinion, as someone who has done quite a few legacy migrations, leaving data behind is an unacceptable option.Good luck! |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2011-09-29 : 03:19:36
|
"Is it possible that the new company is wrong and I will be able to keep this data, or is this most likely right?"My take on this is that the people who should be doing this are the people providing the new ERP system. They know their database inside out, and will be the safest pair of hands to make sure that all the data is migrated to the right tables / columns and to get the mapping right etc.If its a package that is sold thought agents, and there are certified consultants for it, then there shuold be other people who can do the job too.But someone who just knows both VFP and MS SQL is not going to be a "safe pair of hands". Migrating the data between those two systems is technically easy, but getting it all in the right place, correctly cross-linked, is the part that requires application-specific knowledge.You might not like the cost though. Its a time consuming, one off, job. (Bound to be cheaper than all your colleagues messing around with two systems for the next N years, particularly as you get staff turnover and new people aren't trained how to use the old system so can't operate effectively (or new-hires will be trained - that's a huge cost for occasional use, and even then a lack of familiarity with the old system will lead to costly mistakes).But management often take decisions with financial implications by "living with" the ongoing cost, rather than paying the upfront cost.But .. I would seriously question whether the company selling you this system is any better than a Double Glazing Salesman. "Can't be done" means they either have insufficient knowledge of the inner workings of the application, in which case expect their support to be poor, or they aren't prepared to do it - in which case they should be telling you that, and giving reasons why.We expect to import 100% of existing data into our systems when we get a new customer. Where we can't import data we we provide acceptable alternatives. For example, we can't import encrypted passwords from other competitor's systems - if the existing system is done properly the passwords will be stored using a one-way encryption so we can't get the original password back; but we do provide the means for existing customers to securely retrieve their account and set up a new password.Tell your boss he's being given the run-around. I look forward to hearing how this unfolds  |
|
|
|
FTKing
Starting Member
5 Posts |
Posted - 2011-09-29 : 09:31:09
|
| Kristen thank you for the advice. I also agree that it seems like we're not getting a great answer from the provider. I just sent an e-mail to a relevant person at the providing company and I'm hoping he can shed some light on this. Perhaps the sales rep for our area is newer or hasn't done a similar transition or doesn't have the expertise needed to really answer questions. If this is the case I am a bit weary, but we have contacted A LOT of companies using this software and got a positive response from every single one, except one who seems to also now be in the ERP business and wanted to sell me his product. I am confident in the product, and I'll wait to hear back from the employee who should have the right expertise before I really judge the company. With any luck we'll get good news and proceed forward. Thanks again. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2011-09-29 : 11:29:50
|
| Sounds OK then. Salesman should have said "I don't know I'll have to get back to you on that" though ...Lots of salesmen I have worked with just make it up though. Sales Commission is too much much of an incentive. |
|
|
|
|
|
|
|
|
Can't migrate transactions to MS SQL 2008?