Skip to content

Jim Duncan

← ShareGate Feedback Forums

My feedback

1 result found

  1. Create a new PowerShell Command to use the Export metadata feature

    37 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    13 comments  ·  ShareGate migration tool Suggestions » 01- Migration  ·  Admin →
    Jim Duncan supported this idea  · 
    An error occurred while saving the comment
    Jim Duncan commented  · 

    No need for a new cmdlet, just give us a -SkipContentDownload switch parameter for the Export-List cmdlet.

    Consider: Our hourly rate to the customer is $185 and it takes even me (an old hand at this) at least 15 minutes to manually generate each Export file. With 500 libraries to export, that equates to over 125 hours of labor at a customer cost of $23,125 – a sum that effectively kills the cost/benefit of going with ShareGate vs. the competitor.

    However, if the Export-List cmdlet didn’t have to export the terabytes of content to a file system (which the customer has no room for), then I could generate all 500 export files with simply a list of libraries and about 15 minutes worth of PowerShell.

    Hopefully, the IMMENSE difference this would make for such large migrations is now clear and perhaps a conversation could be started internally there at ShareGate (Gsoft) to at least consider it…

Feedback and Knowledge Base

(thinking…)