KB Category: Pimbrook Internal
Migration from (Software) to Sage 50 – Checklist
Migration from (Software) to Sage 50-Checklist
Install Software – Checks
- Check Regional Settings are correct
- Anti Virus Software
- UAC Turned Off
- Install and Configure Software
- Ensure Tax codes are Correct (Irish Settings)
- Is Foreign trader required to be activated
- Have they any UK companies – activate MTD
- E-banking set up
- Set up email for basic layouts
- Set financial year
Software Migrating from (Software)
- Export Stock records and opening stocktake if needed. (Import to Sage 50 section as well)
- Get copy of P&L and B/S as well as the TB (could get extra paid job creating new COA at very least)..I know this COA is in your Checks section
- Agree mapping of Trial Balance with client from existing Nominal codes to Sage 50 codes and Enter to Sage 50.
Software migrating from (Software)
- Export Customers from (Software)
- Export Suppliers from (Software)
- Export Nominal from Sage one
- Report on outstanding transactions in the Bank
- Export Opening balances for Customers
- Export Opening balances for Suppliers
- –
- Export Trial Balance
Sage 50
- Import Customers to Sage 50
- Import Suppliers to Sage 50
- Import Nominal to Sage 50
- Enter outstanding Bank transactions
- Import/Enter Opening balances for Customers
- Import/Enter Opening balances for Suppliers
- Do Journal to cancel out he suspense account entries after entering the opening balance
- Enter Trial Balance
Checks
- Cross check that everything Balances
- Configure COA
- Report Design
How to Use Fiddler to Investigate a Stuck Submission
How to Use Fiddler to Investigate a Stuck Submission
**Please be aware that you cannot change the GUID number or ROSDATA file anymore going forward. If a customer should need to do a submission in a previous period, then the absence of history in the ROSDATA file would stop them from doing that.
If a submission is hanging, the problem is that its stuck at Sage’s RTX server and needs to be pushed through to ROS. You can check this as follows:
Check to see if you are getting error message 500 on Fiddler (steps a – h below)
a. Download and run from https://www.telerik.com/download/fiddler/fiddler4
b. Open Progress TelerickFiddler Web Debuger
c. Select Tools – Options
d.Tick the box for Decrypt HTTPS CONNECT
e. Click OK
f. Log out of Fiddler and the Payroll
g. Log back in to both
h. Drag the icon over payroll
Once you are logged back in you should get the 500 error message. It will give you any error messages in red (on the left of the screen)
Double click on the error and click on RAW on the right hand side and copy the error message into notepad to send with the other details to sage
‘Error 500 – Error retrieving file XXXXXX.zip’ would indicate a problem at Sage RTX Server and you will need to contact Sage to get the submission released.
Error: When running the server update to the M drive – not enough space need 8970 KB free space.
Error: When running the server update to the M drive – not enough space need 8970 KB free space.
When running the server update to the M drive got the following message:
M:\ drive not enough space need 8970 KB free space.
The M drive had 97 GB free
Solution:
Change the dataloc.ini from the mapped drive to the UNC path and the update will run without issue.
.