Migrating from NeatBox

If you are an existing user of the NeatBox local version, you can migrate your data to the NeatHub cloud version.

Migration Overview

NeatHub supports migrating data from the NeatBox local version to the cloud version:

  • All item data
  • Item images
  • Attribute settings
Note

Migration requires contacting the developer — it is not a self-service operation. Please follow the process below.

Before You Migrate

Get Familiar with NeatHub

Before migrating, please familiarize yourself with how NeatHub works:

  • NeatHub is a cloud-based version with data stored in the cloud
  • Features and workflows differ from the NeatBox local version
  • We recommend trying NeatHub first to get comfortable with its features

Understand Membership Restrictions

NeatHub uses a membership model, and some features require a membership:

  • Learn the differences between member and non-member features
  • Decide whether to subscribe based on your needs
  • Some features may require a membership after migration

Confirm Your Data Is Finalized

Before migrating, make sure your NeatBox local data is fully organized:

  • Check that all item information is complete
  • Confirm you no longer need to make changes
  • You cannot re-migrate after modifying local data

Migration Restrictions

One-Time Only

Due to potential data conflicts, migration can only be performed once:

  • You cannot migrate again from the same account after the first migration
  • Make sure your data is finalized before requesting migration
  • Report any issues promptly during the migration process

Attribute Settings Override

During migration, the local version's attribute settings will override the cloud version's settings:

  • If you have already configured an attribute system in NeatHub cloud
  • It will be replaced by the local version's attribute settings after migration
  • We recommend not configuring attributes in NeatHub before migration — just use the local version's configuration
Important

Please make sure you understand the restrictions above before proceeding with the migration request.

Migration Process

Step 1: Try NeatHub

  • Download and install the NeatHub app
  • Register an account and log in
  • Familiarize yourself with NeatHub's features and workflows
  • Understand the membership feature restrictions

Step 2: Confirm Your Data

  • Go back to the NeatBox local version
  • Check that all item data is complete
  • Make any necessary changes to item information
  • Confirm that no further changes are needed

Step 3: Back Up Your Data

  • After trying NeatHub without issues
  • Back up your data from the account page in the NeatBox local version
  • Save the backup file

Step 4: Contact the Developer

  • Send your NeatHub account to the developer
  • The developer will handle the data migration
  • Wait for the migration completion notification

Contact Information

To request data migration, please contact the developer:

  • QQ Groups: 306711791 / 432844532
  • WeChat Official Account: Maozola (猫佐拉)
  • Email: lh9403@icloud.com

Post-Migration Checklist

After migration is complete, we recommend:

  • Log in to NeatHub and check that all items were imported correctly
  • Verify that item images display properly
  • Check that attribute settings are correct
  • Report any issues to the developer promptly

FAQ

Can I migrate from the NeatBox cloud version?

Currently, only migration from the NeatBox local version is supported. Cloud version migration is not available.

Will my local version data be deleted after migration?

No. Migration does not delete your local version data — it remains intact. However, you cannot migrate again to update the data.

How long does migration take?

Migration time depends on the amount of data. It typically takes 1-3 business days. Larger datasets may take longer.

Can I go back to the local version after migration?

Migration is a one-way operation and cannot be reversed. Please confirm before requesting migration.

Recommendation

Migration is a significant operation. Please make sure you are familiar with NeatHub's features, have finalized your data, and understand the migration restrictions before contacting the developer to proceed.