Excel macros and Advanced Filtering Issues after converting to Office 365 and Excel 2016

I have created some macro files and advanced filtering tools internally in my company using Excel 2103. Now that the company has converted users over to 365, many macros take excessive times to run or don't run correct and have incomplete results. Advacned filtering files have severe latency or dont ever return results. All of these worked without issues in Excel 2013. Are there any known fixes,chngges that must occur in the original files or compatability fixes?
Thanks

Thank You I will try this first It was done as an upgrade and not a clean install

HI CK76,
We have still not been able to find a solution to fix the issues after moving into Office 365. I have been trying to focus on one important file that uses advanced filtering and a small amount of code to trigger the filter or clear the sheet The file works as designed in Excel 2013 and on my home system with Excel 2016. In the new work version using 365 and Excel 2016, it takes an excessive amount of time to open if it does at all and I don/t believe it has ever finished the filtering to return results. It shows processing or just clocking.
To date:
We tested backward in Excel 2010 and works OK
We tried running Office Repair with no success
We tried running the file on a new build with 365 and it won't work. This should match your suggestion for doing a clean install.
In addition we have macros that take an extensive amount of time to run compared to in Excel 2013
Large files are slow to open now that has been solved by moving some users to 64 bit.
Any thoughts?

Try checking file options and ensure following.

1. Hardware graphics acceleration is turned off.
2. Multi-Threaded calculation is turned on, use max available core

Then...
1. Check Update Channel of Office 365, ensure you are on either Semi-Annual Channel or Monthly Channel, and updated to latest version
2. Check if you have any macro/add-in with API reference. If there is one, remove and test.

Additionally, try running Excel in safe mode and see if you can at least open the file.

Without detail of your code and workbook, this is as much suggestion as I can come up with. Try contacting MS support with detail of your issue.

Hi CK76,
I wanted to let you know what finally worked. We tested the 2013 file in Excel 2016 with WIN 10 and no good, tested on a bran new PC with 365/Excel 2016 and no good. Excel 2013 and 2010 worked fine. The final solution was to save the file in 2013, open it with 365./excel 2016 and run a sheet compare tool. A colleague did this task and he waasnt sure what if anything occured, but the file now runs in 365/2016. I'm not familiar with the sheet compare function myself. Thank you for the help

Thanks for the update Glad you got it solved.

Though still odd that sheet compare fixed it. I don't think that really changes anything