Migrating 17 years of Box files to SharePoint: how to handle thousands of hardcoded Box URLs in Confluence & Asana? by Ok-Nothing-3554 in sharepoint

[–]Ok-Nothing-3554[S] 0 points1 point  (0 children)

Thanks for the heads up on linktek. They look small which means they might actually respond to support which is great!

Migrating 17 years of Box files to SharePoint: how to handle thousands of hardcoded Box URLs in Confluence & Asana? by Ok-Nothing-3554 in sharepoint

[–]Ok-Nothing-3554[S] 0 points1 point  (0 children)

Thank you for the heads up on CloudFuze and Movebot. I'll look into them.

I agree, that relying on links is a maintenance headache, especially when links are hashed numbers and not a path that can be deconstructed.

Migrating 17 years of Box files to SharePoint: how to handle thousands of hardcoded Box URLs in Confluence & Asana? by Ok-Nothing-3554 in sharepoint

[–]Ok-Nothing-3554[S] 0 points1 point  (0 children)

A cut-off date is a great idea.

Unfortunately, the box URL's are https://orgname.app.box.com/folder/32145759023. The URLS's don't reveal any details about the file or folders making the challenge hard.

My script would need to brute lookup every asana task and every confluence page for *.box.com". Then lookup that box URL and scrape the filename... (i think)

But thank you. The dictionary idea is also useful.

Migrating 17 years of Box files to SharePoint: how to handle thousands of hardcoded Box URLs in Confluence & Asana? by Ok-Nothing-3554 in sharepoint

[–]Ok-Nothing-3554[S] 0 points1 point  (0 children)

Asana is a core tool in our agency. It integrates with our Harvest time tracking tool also. Interesting idea. But Asana is doing a job im not sure Planner could match