by Andrew Karasev
 

1. Great Plains Integration Manager - this is rather end-user tool - it is very intuitive, it validates 100% of business logic, brings in/updates master records (accounts, employees, customers, vendors. etc.) brings in transactions into work tables.  The limitation of Integration Manager - it does use GP windows behind the scenes without showing them - so it is relatively slow - you can bring 100 records for ongoing integration - for one-time conversion/integration you are probably OK with IM.  By the way you can program Integration Manager with VBA.
2. eConnect – it is type of Software Development Kit with samples in VB.Net.  Obviously the development environment should be Visual Studio.Net.  eConnect will allow you to integrate master records - such as new customers, vendors, employees, etc., plus you can bring transactions into so called Great Plains work tables (eConnect doesn't allow you to bring open or historical records - you need to post work records in Great Plains, the same limitation applies to Integration Manager above).  eConnect is rather for ongoing integration.  It was initially created for eCommerce application integration to Great Plains.
3. SQL Stored Procedures.  Obviously you have unlimited control and possibilities with SQL queries.  You need to know Great Plains tables structure and data flow.  Launch Great Plains and go to Tools->Resource Description->Tables.  Find the table in the proper series.  If you are looking for the customers – it should be RM00101 – customer master file.  If you need historical Sales Order Processing documents – they are in SOP30200 – Sales History Header file, etc.   Do not change existing tables - do not create new fields, etc.  Also you need to realize that each GP table has DEX_ROW_ID - identity column.  For ongoing integrations - sometimes it is good idea to use inbound/outbound XML in the parameters - then you can deploy web service as a middle party between two systems.
4. Data Transformation Services (DTS) – Good tool for importing your third party data into staging tables in GP - then you can pull them in using either stored procs of Integration Manager.  You can also deploy this tool for EDI export/import.
5. Great Plains Dexterity Conversion Utilities.  If your legacy data sits in old Dexterity customization on Ctree/Pervasice.SQL/Btrieve - you can create custom  Dexterity conversion utility, which will read the table in Ctree/Btrieve and will move it to SQL based new custom Dexterity table.  In this scenario - you need Dexterity customization upgrade as well.  (Great Plains Dexterity - is programming language and technology of former Great Plains Software - Microsoft Great Plains is written in Dexterity)
6. MS Access – if you are doing one time conversion and your legacy has old ODBC compliant platform - you can use MS Access to create linked tables there - or import into MS Access.
7. SQL Linked Servers – you can do direct SQL queries to other ODBC compliant platform via SQL Linked Server (including ORACLE, UNIDATA, Pervasive SQL, Ctree, etc) - you may need to familiarize yourself with OPENROWSET command in Transact SQL.  This is also good option if you need cross-platform Crystal Report - pulling data from SQL Server and third party databases on the same report.
8. MS Excel - yes - sometime you can use it for legacy data massage before feeding it into Great Plains.
9. Warning - do not place existing GP tables into Replication! - you will have upgrade issues.