BoilerBackpack with Syncplicity storage service retirement now set for Oct. 31

BoilerBackpack powered by Syncplicity, a file storage, syncing and sharing service Purdue began offering to faculty, staff and students in 2012, is now set to be retired Oct. 31.

Once BoilerBackpack is retired, users still will be able to access their files through individual accounts that ITaP plans to set up on Purdue’s storage system, although the syncing and sharing features of Syncplicity will no longer be available.

Purdue users now have free access to Microsoft’s OneDrive for Business, which is available to the campus community at no cost and offers syncing and sharing features. OneDrive for Business also offers faculty, staff and students a terabyte of space each, while BoilerBackpack has offered 150 gigabytes, one-seventh of OneDrive for Business’s capacity.

Users are welcome to move stored files that they want to keep to OneDrive for Business or another storage option now if they prefer. They will be able to do so after Oct. 31 as well.

For information on setting up Office 365 with OneDrive for Business through Purdue visit

For information on transferring files from BoilerBackpack to OneDrive for Business, as well as sharing and syncing files and using OneDrive for Business with iOS, Android, macOS and Windows, see

ITaP plans to retire BoilerBackpack because the Purdue’s licensing of Office 365 includes OneDrive for Business storage. Eliminating a redundant service like BoilerBackpack is in keeping with Purdue’s goal of cost reduction and affordability.

For more information and assistance, contact Tech Support at the ITaP Customer Service Center by calling 49-44000 or emailing

Writer: Greg Kline, science and technology writer, Information Technology at Purdue (ITaP), 765-494-8167 (office), 765-426-8545 (mobile),

Last updated: Aug. 31, 2017

Purdue University, 610 Purdue Mall, West Lafayette, IN 47907, (765) 494-4600

© 2015 Purdue University | An equal access/equal opportunity university | Copyright Complaints | Maintained by ITaP

Trouble with this page? Disability-related accessibility issue? Please contact ITaP at