Delta Pass for Google Sites Migration

Migrate only changed content after the initial migration to SharePoint.

Last updated: 2025-01-15 General Info

Delta Migration Process

πŸ“‹
Initial Pass
Full migration
β†’
πŸ”
Check Changes
IDs & dates
β†’
πŸ”„
Delta Pass
New/modified only
β†’
βœ…
Cutover
Final sync

Overview

Delta pass (or incremental migration) allows you to migrate only new and modified content after the initial migration is complete. This is useful for keeping the target site up-to-date while users continue working in the source environment.

Migration Tool Purpose

Cloudiway is designed as a migration tool intended for an initial migration, a few delta passes, and cutoverβ€”not as a long-term synchronization solution between platforms.

How Delta Migration Works

The Cloudiway platform tracks migrated items internally by storing item IDs and modification dates. On subsequent migration runs, the system performs these checks:

πŸ†•

New Items

If an item ID isn't found in the cache, the item is identified as new and gets migrated to the target site.

πŸ“

Modified Items

If an ID exists in the cache but the source modification date is newer than the stored value, the item is overwritten in the target.

⏭️

Unchanged Items

Items with matching IDs and modification dates are skipped, saving time and resources.

Cache Persistence

Even if you clean up the target site, the internal cache remains intact for that migration, allowing subsequent delta passes to function correctly.

Key Limitations

⏱️ 90-Day Time Window

Once an initial migration pass is completed, you can run delta passes for up to 90 days. After this period, the migration must be restarted from scratch.

πŸ” Limited Permission Updates

During delta passes, only permission changes on sites level are remigrated. Page-level or item-level permission changes may not be captured.

πŸ—‘οΈ Deletions Not Propagated

Deletions on the source tenant are not propagated to the target tenant during delta passes. Items deleted in Google Sites will remain in SharePoint.

Not for Long-Term Sync

If you need ongoing synchronization between Google Sites and SharePoint, consider a coexistence solution rather than relying on delta migrations.

Best Practices

Do

  • βœ“ Plan your migration timeline within 90 days
  • βœ“ Run delta passes periodically before cutover
  • βœ“ Schedule final delta pass close to cutover
  • βœ“ Document what won't be synced during delta

Don't

  • βœ— Rely on delta for permanent synchronization
  • βœ— Expect deletions to propagate automatically
  • βœ— Wait more than 90 days between passes
  • βœ— Assume all permission changes will sync

Recommended Workflow

  1. 1 Complete initial migration during a maintenance window
  2. 2 Run delta passes weekly or bi-weekly during transition period
  3. 3 Schedule final delta pass 24-48 hours before cutover
  4. 4 Manually handle any deletions or permission changes as needed
  5. 5 Switch users to SharePoint and decommission Google Sites

Was this article helpful?

We value your feedback

Help us improve your experience

What would you like to share with us?

Need direct support? Open a ticket