Migration Guide

FanUpdate to Luster

Import public blog entries from FanUpdate into Luster’s News Feed add-on.

Important!

Before You Start

  • Backup your FanUpdate database! Do not delete it until you have manually checked that your data has imported correctly. Keep the old database longer if you want extra reassurance. (Your FanUpdate install is not deleted or changed.)
  • Backup your Luster database (if you've already settled into Luster)

FanUpdate imports are smaller than the other imports. FanUpdate is not used for members or owned listings here. It only moves public update/blog entries.

FanUpdate commonly uses a main blog table named: blog. It may also use related tables like: blog_category or blog_catjoin. If your FanUpdate table has a different name, the wizard lets you enter it.

Import Scope

What Is Imported

What Luster Imports

  • Public blog entries
  • Entry title
  • Entry body
  • Posted date
  • Fanlisting assignment when Luster can match the fanlisting title

What Luster Does Not Import

Luster does not import:

  • Non-public entries
  • FanUpdate comments
  • FanUpdate smilies
  • FanUpdate display options
  • FanUpdate admin accounts
  • FanUpdate settings that do not belong in Luster’s News Feed
  • Other FanUpdate features such as news or events
This importer is intentionally focused.

It imports blog/update entries only. Use the Enthusiast, Listing Admin, or Fanatically importers for members and owned listings.

Walkthrough

Step-by-Step Import Instructions

  1. Import or Create Owned Listings First

    Before using the FanUpdate import, make sure the matching fanlistings already exist in Luster.

    If your main fanlisting data is in Enthusiast, Listing Admin, or Fanatically, import that first.

  2. Open the Import Wizard

    In the Luster admin panel, go to Import Data → FanUpdate.

  3. Connect to FanUpdate

    On the Connect step, choose how Luster should read your old data. You have two main choices:

    • Use Live database connection if your old FanUpdate database is still available on the same server or your host allows database connections. In most cases, leave your Host as localhost.
    • Use Upload SQL dump if you exported FanUpdate from phpMyAdmin or with mysqldump. The file should end in .sql:

  4. Enter the Blog Table Name

    On the Options step, enter the FanUpdate blog table name. Most installs use blog.

    Luster will look for the main table plus related tables based on that name:

    Blog table name you enter Luster looks for
    blog blog, blog_category, blog_catjoin
    updates updates, updates_category, updates_catjoin

  5. Choose What to Import

    FanUpdate has one import option: Blog entries to News Feed. Keep it selected.

  6. Preview the Import

    The Preview step shows how many entries Luster found. Skipped entries are usually non-public entries.

  7. Run the Import

    When the Preview looks right, run the import. The Done step shows how many updates were imported and skipped.

Troubleshooting

Edge Cases & FAQ

Non-public entries were skipped

FanUpdate entries marked non-public are not imported. This is expected. Luster only imports public entries from FanUpdate.

Comments are missing

FanUpdate comments do not have a Luster News Feed equivalent, so they are not imported.

Smilies are missing

FanUpdate smilies are not imported. The update text itself still imports.

Entries imported as collective-level updates

If Luster cannot match a FanUpdate fanlisting title to a Luster listing title, the entry imports without a specific listing. You can edit the update in Luster afterward if you want to attach it manually.

Multiple fanlisting assignments

If one FanUpdate entry is linked to more than one fanlisting, Luster may create an update row for each matched listing.

Does this import members/listings/etc?

No. FanUpdate imports only update/blog entries.

Why does Luster need the News Feed add-on?

Because FanUpdate entries become Luster News Feed entries, and the addon needs to be enabled for your to manage them. Luster is automatically installed with the News Feed addon enabled, so it should be there unless you disabled it via Manage Addons yourself.

Should I import FanUpdate before or after listings?

If you want updates attached to specific fanlistings, import or create your owned listings first. If you only need collective-level updates, the listing match is less important.

Can I run the FanUpdate import more than once?

Yes. Use Skip when re-running to avoid duplicating existing updates.

Why did some entries skip?

Most skipped entries are non-public entries or entries already imported when using the Skip conflict strategy.

Can I import FanUpdate comments later?

Not with the current importer. FanUpdate comments do not have a matching Luster feature.

When can I remove FanUpdate?

Wait until you have checked your imported updates in Luster. Keep a backup even after removing the old files.