Incremental migration

 


These articles are abridged from my  book on Office to Apps migration. 

Going GASfrom VBA to Google Apps Script.

Now available  directly from O'Reilly or Amazon.

All code samples can be found on Github. Note that that VBA samples have been developed for Office for Windows and may need some tweaking for Office for Mac.

What is incremental migration ?


The process of migrating assets and workflow from Office to Apps is fairly straightforward. 

https://sites.google.com/a/mcpher.com/share/Home/excelquirks/goinggas/exap/incremental/Screenshot%202015-09-25%20at%2020.02.10.png


The ‘magic happens’ step is not so hard for as long as you don’t have VBA automation and documents which are dependent on each other.


Sets of documents with dependencies that can be isolated can of course be migrated. But this is more complicated as it usually involves coordination between processes and groups of people, but nevertheless, if a cutover period is tolerable and can be scheduled and the dependencies manageable, it can be done. 


 

When there are documents, automated processes and data that span multiple subject areas and migration timetables that cannot be coordinated, a different process is needed. One in which assets can be partially moved, and automation which can be incrementally delegated. 

VBA Migration process

This is an example of some VBA automation that accesses or maintains various Excel workbooks. The data and logic modules represent the pieces of VBA code that access the data or contain the business process logic for manipulating the data. 



There may be various reasons that this entire process cannot be scheduled to happen all at once. Some examples could be;
  • The workbooks(s) may be shared with a different subject group or process which is not ready to migrate.
  • The automation may access databases or other resources which are not scheduled to move to Apps.
  • There is no resource available to migrate the processing from VBA to Apps Script, but a need to move the workbooks to Sheets to support a subject group or process that has already moved. 

The Execution API

This API allows assets and automation to be migrated a chunk at a time. 




For example;

Workbooks can be migrated to Sheets but still accessed from VBA by simply substituting the data access code in VBA to delegate data access to Apps Script. 



Some or all of the logic functions can be migrated to be executed by Apps Script, returning the result to VBA for orchestration



All code samples can be found on Github. Note that that VBA samples have been developed for Office for Windows and may need some tweaking for Office for Mac.

Other items in this section

For more like this, see Execution API and Office to Apps migration. Why not join our forumfollow the blog or follow me on twitter to ensure you get updates when they are available. 

You want to learn Google Apps Script?

Learning Apps Script, (and transitioning from VBA) are covered comprehensively in my my book, Going Gas - from VBA to Apps script, available All formats are available now from O'Reilly,Amazon and all good bookshops. You can also read a preview on O'Reilly

If you prefer Video style learning I also have two courses available. also published by O'Reilly.
Google Apps Script for Developers and Google Apps Script for Beginners.




Comments