Welcome to Backendless! We would love to be a backend of your choice. This is an evolving document which is updated as we iterate over features and simplify the Parse-to-Backendless migration process. Our goal is to make the transition as smooth as possible and we greatly rely on your feedback.
We conducted a webinar on the topic of migration from Parse to Backendless. We recommend watching the webinar to become more familiar with Backendless and the migration process. There were a lot of answered questions and we hope you will find the recording useful:
Migration of data objects from Parse to Backendless is possible through the Export/Import procedure. Backendless implements a special data import algorithm for processing Parse’s export files and migrating user accounts, data objects, geopoints and files into Backendless. The import procedure should handle about 99% of possible deployment scenarios. If you however, you experience an error during the import or the data tables are not fully imported, please upload the Parse’s export file to either Dropbox or Google Drive and send the link to email@example.com so we can investigate it further.
Similar to Parse, Backendless offers a hosting service for your application files. Unlike Parse, the hosting service can contain both static and dynamic (node.js) content. Parse dashboard does not contain File Browser and unfortunately there is no API to retrieve file listings from the Parse’s storage. This makes the migration of the files cumbersome. You can upload individual files to Backendless either using the API or with Backendless Console. It should be fairly straight-forward to create a script that accepts a listing of URLs of files hosted in Parse and uploads each of them to Backendless.
Backendless supports push notifications for Android, iOS and Windows Phone devices. To migrate your push notification functionality, you need to perform the following changes:
Similar to Parse, Backendless stores user accounts in a special “Users” table. When you perform data import into Backendless, the user accounts will be recreated in Backendless as well. As for roles, Backendless maintains them separately (there is no specialized table for roles). Instead, they are available in the Users > Security & Permissions section of Backendless Console:
The data import procedure will import the roles so they are recognized by Backendless.
Backendless offers richer API support for social logins. Our APIs and the backend support include the complexity that otherwise would need to be in your app. There are two approaches available in Backendless. One is without Facebook/Twitter SDKs (it is called “easy login”) and the other with FB/Twitter SDKs. The following documentation describes the approaches and the configuration steps you need to go through to configure the backend:
We use the term “Server code” and “Business logic” for the functionality Parse calls “Cloud Code”. Backendless supports three server-side languages: Java, PHP and JS(Node.js). Custom code on the server-side falls into the following categories:
The primary difference between Parse and Backendless jobs/timers is the duration a timer can run for. Backendless free tier limits it to 5 seconds. It can be expanded to 20 seconds with a “Function Pack” available in Backendless Marketplace (click Marketplace in Backendless Console and select the Business Logic category).
Currently webhooks are not supported. We are adding support for this functionality. It should be available in the next 3-4 weeks.