Sage 100

Has anyone used the SMI connector module to bring in data from QB to run reports? Trying to talk a customer out of bringing QB history into MAS...

Quote it cost plus a very large number so they get the hint..........

we tried that, now they are convinced they want to input everything manually....

Stress the importance of them testing -- and providing you a sign-off that they've reviewed the history and it's accurate. If you do not do this step there's a high likelihood that they will come back in 9 months having found all manner of inaccuracies. I've taken over one or two accounts where a partner tried to import significant history. It never seems to end well because there's not enough time for the customer to check it - so they don't - and then when they stumble across a problem it's seen as your fault.

IN the testing area. We now require a spec for ""control reports"" in migrations. We define the Sage 100 reports that define the imported data (B/S, Customer Sales, Open SO, etc) and then define the reports on legacy system to match. We go through the matching in the trial to prove concept, and the final numbers after go live. It has eliminated the time bombs. You might use something similar in this process.

Have you worked with them to define how having that history in Sage will make them money? What the circumstances are? Maybe offer the alternative of creating a spreadsheet with period balances which produce the DR & CR (separate columns) programatically. They can then manually enter the big JE. A couple days of them struggling with that ""easy"" process could open their eyes.

Thanks Everyone - I like the idea of the ""control reports""...

As for SMI connecting to QB, as long as you have an ODBC or OLEDB connection, you should be able to do it.