Guide sections

VTT import overview

Compare Fantasy Grounds, Foundry, Roll20, and PDF import paths before choosing the right one for your campaign.

Currently supported

SourceImports FromWhat Imports
Fantasy GroundsCampaign folder (db.xml)NPCs, locations, encounters, items, images
Foundry VTTExported files (actors/items/scenes JSON + journal.db)NPCs, items, locations, journal content
Roll20Character Vault JSON or CSVCharacters -> NPCs only
PDFAdventure or sourcebook PDFAI-extracted creations or game-system rules

-> Fantasy Grounds import guide -> Foundry import guide -> Roll20 import guide -> PDF adventure import

PDF import uses AI extraction and needs an AI subscription (Companion or Power). The VTT file imports (Fantasy Grounds, Foundry, Roll20) parse your data locally and work without a subscription.


Where imports land: the master library

VTT imports don’t drop straight into a campaign. They land in your campaign-neutral Master Library - a shared catalog that sits alongside your campaigns rather than inside any one of them. Re-importing the same module doesn’t pile up duplicates: the Library recognizes the source and only adds creations it hasn’t seen before.

To use an imported creation at your table, open it in the Library and choose Assign to Campaign. That drops an editable copy into the campaign you pick while the Library master stays the original, untouched. You can assign the same creation to more than one campaign; assigning it to the same campaign twice returns the existing copy rather than making a duplicate.


Why import?

Save hours of work

If you’ve built campaigns in a VTT, you have data - NPCs with descriptions, items with properties, notes and story entries. Importing brings all of that into Campaign Familiar so you can:

  • Enhance with AI-assisted features
  • Build relationships between creations
  • Use Quick Prep for new content that fits your existing world

Better prep tools

VTTs are great for running games. Campaign Familiar is built for preparing them. Import your VTT data to get:

  • Campaign-wide search
  • Relationship visualization (Connection Map)
  • AI generation that knows your world
  • Session planning linked to your content

Keep using your VTT

Import doesn’t mean abandoning your VTT. Use Campaign Familiar for prep and organization, then run your sessions in whatever VTT you prefer.


What imports

Import coverage varies by source. The table below shows what each can produce; check each platform’s guide for the exact list.

Creations

Content TypeBecomesNotes
NPCs/CharactersNPC creationsAll sources
Locations/PlacesLocation creationsFantasy Grounds, Foundry, PDF
Items/EquipmentItem creationsFantasy Grounds, Foundry, PDF
EncountersEncounter creationsFantasy Grounds, PDF
Story entries/JournalsNarrative content or campaign markersFoundry journals, PDF

Metadata

DataImport Status
Names and descriptions✓ Always imported
Stats and properties✓ When available
Images✓ When available
Relationships◐ Limited (recreate in Campaign Familiar)
Custom fields◐ Varies by source

What doesn’t import

Some content stays in your VTT:

  • Maps - Campaign Familiar doesn’t have a map viewer; keep maps in your VTT
  • Character sheets - Detailed PC mechanics stay in your VTT
  • Automation/Macros - VTT-specific scripting
  • Audio/Video - Multimedia assets

Campaign Familiar focuses on narrative content - the people, places, and stories - not tactical game mechanics.


Import process overview

All imports follow this general flow:

1. locate export/data

Find your source files:

  • Fantasy Grounds: Campaign folders in the SmiteWorks directory
  • Foundry: Export your world’s actors, items, scenes, and journal to JSON first
  • Roll20: Export a Character Vault JSON or a character-sheet CSV first

2. start import wizard

  1. Open Campaign Familiar
  2. Open the Library from the sidebar and click Import to Library
  3. Select your source (Fantasy Grounds, Foundry, Roll20, or PDF)
  4. Navigate to your campaign data or export file

3. preview and configure

Campaign Familiar shows what will be imported:

  • Review creation counts
  • See any warnings or conflicts
  • Configure import options

4. import to the library

Click import and wait. Large campaigns may take a minute or two. Everything lands in your campaign-neutral Master Library, not in a specific campaign.

5. assign to a campaign

Open an imported creation in the Library and click Assign to Campaign to place an editable copy in the campaign you choose. The Library master stays the original, so you can assign the same creation to more than one campaign - and assigning it to the same campaign twice returns the existing copy instead of duplicating it.

6. review and organize

After importing (and assigning what you need):

  • Check imported creations for accuracy
  • Add tags to organize content - on the Library master, on the assigned campaign copy, or both
  • Create relationships between creations in the campaign you assigned them to
  • Fill in any gaps with AI generation

Post-import recommendations

Clean up imported data

VTT data often has quirks:

  • Duplicate entries - Merge or delete
  • Incomplete entries - Add missing details
  • Naming inconsistencies - Standardize

Add relationships

VTTs don’t export relationship data. In Campaign Familiar:

  1. Open key NPCs
  2. Add relationships to other NPCs, locations, factions
  3. Use the connection map to see connections forming

Tag everything

Import doesn’t know your organizational system. Add tags:

  • imported - Track what came from the VTT
  • Story arc tags - Group by plot line
  • Status tags - needs-review, cleaned-up

Use AI enhancement

On Companion/Power tiers:

  • Generate missing content for sparse entries
  • Let AI suggest relationships
  • Use Session Companion to flesh out imported NPCs

Platform-specific guides

Fantasy Grounds

Fantasy Grounds stores campaigns in a specific directory structure. The import reads your campaign’s XML files (db.xml) and converts them to Campaign Familiar creations.

-> Fantasy Grounds import

Foundry VTT

Foundry import reads exported JSON files - your actors, items, scenes, and journal entries. Export from Foundry first, then point the wizard at the folder containing those JSON files.

-> Foundry import

Roll20

Roll20 import reads a Character Vault JSON export or a character-sheet CSV. It brings in characters as NPCs.

-> Roll20 import

PDF

Import a PDF adventure to have the engine extract NPCs, locations, items, and more - or a sourcebook PDF to teach the engine your game’s rules.

-> PDF adventure import · Game system rules


Troubleshooting imports

Import fails completely

  • Verify you selected the correct campaign folder
  • Check that the campaign data isn’t corrupted
  • Try exporting from your VTT first, then importing the export

Missing content

  • Some VTT data may not map to Campaign Familiar creations
  • Check VTT-specific documentation for known limitations
  • Manually create what didn’t import

Garbled text

  • Character encoding issues - try re-exporting from VTT
  • Special characters may not survive the conversion
  • Edit affected entries manually

Duplicates

  • Import may create new entries even if similar ones exist
  • Use search to find and merge duplicates
  • Consider tagging imports (imported-fg) to identify them