This approach is wrong in principle.
Don't export any controls to any documents; export data.
You should have a distinct data layer. Data layer can be bound to UI. If you don't use formal binding, the idea is the same, only implemented "manually": you populate data to you data grid, use events in your data grid to invalidate/update the data layer. In this way, you support synchronization between UI controls and data.
If this is done this way, you always use data persistence, data export/import, reporting, printing and similar functionality on data layer and never on UI controls.
I suggest you learn and analyze applicability of the following
architectural patterns (
http://en.wikipedia.org/wiki/Architectural_pattern_(computer_science)[
^]):
MVVM — Model View View Model,
http://en.wikipedia.org/wiki/Model_View_ViewModel[^],
MVC — Model-View-Controller,
http://en.wikipedia.org/wiki/Model-view-controller[^]),
MVA — Model-View-Adapter,
http://en.wikipedia.org/wiki/Model–view–adapter[^],
MVP — Model-View-Presenter,
http://en.wikipedia.org/wiki/Model-view-presenter[^].
Pay attention for the motivation of those architectures. If you understand it, you would be able to create better design ideas.
—SA