Event Migration Guide

Documentation
1

With Smoke Signal’s 1-year anniversary update, all events now use the new Lexicon Community data structures for enhanced functionality and better compatibility with other applications. While your existing legacy events remain viewable, you’ll need to migrate them to the new format to manage events and RSVPs effectively.

What You Need to Know

  • Legacy events are preserved: The migration process doesn’t delete your original event
  • Same URL: Your migrated event keeps the same web address
  • Enhanced features: The new format provides better compatibility and additional functionality
  • Limited legacy interaction: Legacy events can only be viewed, not managed
  • :warning: RSVPs not migrated: Existing RSVPs from other attendees are not automatically transferred to the migrated event

Migration Process

Step 1: Access Your Legacy Event

When you’re logged in and viewing a legacy event, you’ll see a notice at the top indicating “You are viewing a older version of this event” along with a blue button labeled “Migrate to Lexicon Community Event”.

image
image1403×695 75.2 KB

Step 2: Initiate Migration

Click the “Migrate to Lexicon Community Event” button to begin the migration process.

Step 3: Migration Confirmation

After clicking the migration button, you’ll see a confirmation page titled “Event Migration Complete” with:

  • A green checkmark confirming successful migration
  • Migration details including:
    • Source Format: events.smokesignal.calendar.event
    • Target Format: community.lexicon.calendar.event
    • Source AT-URI: Your original event identifier
    • New AT-URI: Your new event identifier

image
image1411×594 98.4 KB

Step 4: Access Your Migrated Event

Click “View Migrated Event” to access your newly migrated event, or “Back to Profile” to return to your profile page.

Technical Details

The migration creates a “sidecar” or “sibling” record using the same record key as your original event. This means:

  • Your original legacy event data remains intact
  • A new event record is created in the Lexicon Community format
  • Both records share the same URL
  • The new format takes precedence for all management functions

Important Notes

  • No data loss: Your original event information is preserved during migration
  • One-time process: Each event only needs to be migrated once
  • Immediate access: Your migrated event is ready to use immediately
  • Full functionality: Migrated events support all current Smoke Signal features including RSVP management
  • :warning: RSVP Migration Limitation: While your event details are fully migrated, existing RSVPs from attendees are not automatically transferred. Attendees will need to RSVP again to the migrated event if they wish to confirm their attendance

Need Help?

If you encounter any issues during migration, visit Smoke Signal Feedback.