Sage 50 Accounting [US Edition] GUMU converts the following information from Sage 50 Accounting (formerly known as Sage PeachTree) into

Transcription

1 GUMU for Sage 300 ERP - Sage 50 Accounting [US Edition] Migration Feature List Have your clients been postponing a move to Sage 300 ERP (formerly known as Sage Accpac ERP)because of the costs involved in changing software? Greytrix helps take the pain, hassle, and expense out of migrating data by providing Sage partners with a robust and affordable migration service. And since Greytrix is a channel focused company and works only with Business Partners you can rest assured you will remain in control of the client relationship. Using Greytrix as your Migration Service expert, you can focus your time helping your clients get their businesses up and running on Sage 300 and leave migrating data to us. Versions Supported: Sage 50 Accounting [US Edition] Sage 300 ERP Version 2010 Onwards 6.0 Onwards Editions All Editions All Editions Note: For earlier Version/Editions contact Greytrix. GUMU converts the following information from Sage 50 Accounting (formerly known as Sage PeachTree) into Sage 300 ERP. General Ledger: Chart of Accounts G/L Budget G/L Transaction History of 2 fiscal years (i.e. Current and Previous Fiscal year)* Bank Services: Bank Master: GUMU migrates the G/L Accounts of type Cash in Sage 50 Accounting as Banks in Sage 300 ERP. Bank Balances: GUMU creates single Adjustment unposted Bank entry to bring in opening balance of each bank. 1

2 Tax Services: GUMU converts PeachTree Tax Authority and Tax Codes as Tax Authority, Tax Class, Tax Rate, and Tax Group in Sage 300 ERP. Accounts Receivable: Customer Master Ship to Notes and Comments AR terms Sales person master (no commission information) Custom fields Customer Transaction (History* and Open Transactions):- If user opts just for the Open transactions then GUMU create a summary type document of the open balance in Sage 300 ERP using the following mapping for various types of transactions:- Sage 50 Accounting Transaction Type Unapplied Cash If user opts for History then All s, Payments, and Adjustments are brought into Sage 300 ERP from Sage 50 Accounting in details. Greytrix uses the following mapping for various types of transactions:- Sage 50 Accounting Transaction Type Payment OE OE AR Receipts/AR Refunds *Please Note: - Historical detailed sales invoices are brought in as OE Shipment and hence are available to be viewed in Sage 300 from OE Shipment Entry and OE Entry Screen. The order information for the invoices is not converted for the shipped SO. GUMU updates the Inventory on Hand in Inventory Control Module. Accounts Payable: Vendor Master Custom fields Notes and Comments AP Terms Vendor Transactions (History* and Open Transactions):- 2

3 If user opts just for the Open transactions then GUMU create a summary type document of the open balance in Sage 300 ERP using the following mapping for various types of transactions:- Sage 50 Accounting Transaction Type If user opts for History then All s, Payments, and Adjustments are brought into Sage 300 ERP from Sage 50 Accounting in details. Greytrix uses the following mapping for various types of transactions:- Sage 50 Accounting Transaction Type Item receipt Payment PO Receipt/PO PO Credit note PO Receipt AP payment *Please Note Historical detailed purchase invoices are brought in as PO Receipts and hence are available to be viewed in Sage 300 from PO Receipts Entry and PO Entry Screen. The order information for the invoices is not converted for the received PO. GUMU updates the Inventory on Hand in Inventory Control Module. Inventory Control: Item Master: Following is the mapping of the Types of Sage 50 Accounting Items created in Sage 300 ERP. Sage 50 Accounting Item Type Item Assembly Substock Serialized Item Serialized Assembly Non- Item Service Labor Activity Item Description Only Charge Item Sage 300 ERP Item Type Miscellaneous Charges 3

4 Custom Fields Price List Item On Hand (A single opening balance entry for the Quantity on hand of stock items) Order Entry: Open Sales Order: Only open sales order including its open details is migrated as open sales order detail. Historical detailed sales invoices are brought in as OE Shipments. The order information for the invoices is not converted for the Shipped Sales Orders. Purchase Orders: Open Purchase Order: Only open purchase order including its open details is migrated as open purchase order detail. Historical detailed purchase invoices are brought in as PO Receipts. The order information for the invoices is not converted for the Received Purchase Orders. For Videos on our GUMU Solutions Visit the Greytrix YouTube Channel at 4

5 About GUMU GUMU is a data frame providing migration and integration solutions created by Greytrix. GUMU using web enabled or desktop applications can integrate the systems bi- directionally as well as migrate the information from current less efficient to more powerful and robust system. GUMU has served the organizations who wish to take a giant leap in the process which drives its organization, IT being an invariable parameter of it. GUMU has reached tens of thousands of its users, who are now celebrating its presence, as GUMU has empowered their business information flow process and projected the exponential growth of their business. About The Greytrix Company We are the only company in the world with a unique business model which is reseller centric for providing vertical addons, integration and migration solutions as well as a one stop service for MULTIPLE product lines in the SME segment. We started at a time, when the entire IT industry was moving towards the Dot Coms (ended up being dot bombs!) but decided to take the road less travelled and entered the SME business application market, adding a fresh, new and unique way of facilitating businesses in this segment. l For Further details or Clarifications kindly contact us at - erpmig@greytrix.com Greytrix: - Sage CRM Blog - Sage ERP X3 Blog - Sage 100 / ACT Blog - Sage 300 ERP Blog - * Greytrix, Sage and GUMU TM product or service names mentioned herein are registered trademarks and are properties of their respective owners. *All other names, logos and trademarks are properties of their respective owners. 5