Best Practices for Migrating Pathfinder to Paizo, NEXUS, Foundry, Fantasy Grounds

Kick off your migration by deciding which Paizo assets you need: Paizo Store purchases and official PDFs, Demiplane NEXUS access, the Foundry Community pf2e system, and Fantasy Grounds modules. That action-focused list is the roadmap for every GM and event organizer moving Pathfinder into modern toolchains, and it keeps you from rebuilding material you already own.

Why migrate and what changes for play You are migrating to save prep time, reduce table errors, and make large events repeatable. Paizo PDFs are the authoritative text for spells, monsters, and class features, while Demiplane NEXUS provides a centralized, licensed delivery ecosystem. Foundry’s community pf2e system is where many groups host live games with automated rolls and compendia, and Fantasy Grounds remains a common choice for organized play with module-level packaging. Each platform interprets rules text slightly differently, so you must treat migration as a rules-integration project, not a file move.

Paizo Store and PDFs: source of truth Begin with purchases from the Paizo Store or the official PDFs you already own. Use those PDFs as the ground truth for errata, trait names, and rule text. When you prepare statblocks, cross-check every ability, trait name, weakness, resistance, and damage expression against the PDF text so you don’t introduce transcription errors that change game balance. Keep a simple change log that records PDF page numbers and the errata you applied: this becomes essential when an official errata clarifies how a damage type or resistance stacks during play.

Demiplane NEXUS: licensing and distribution Demiplane NEXUS is a distribution and license layer you must treat as more than a hosting solution. Confirm which products you are allowed to host or link through NEXUS for your group or event, and align purchases to seat counts for live sessions. For conventions and ticketed events, verify NEXUS license terms well before the event: licensing limits will dictate whether you can distribute handouts or require individual purchases. Plan your event library in NEXUS by foldering modules and player-facing PDFs so GMs can grant access quickly without re-uploading files.

Foundry Community pf2e system: automation and compendia Foundry with the community-maintained pf2e system gives you the deepest automation potential, but it also demands careful data hygiene. Build compendia entries from the Paizo PDFs, not from scraped web text, and standardize names for conditions, damage types, and trait tags. Test each monster and NPC in a sandbox scene focusing on these interactions: apply a weakness, then a resistance, then persistent damage to confirm numerical results match the PDFs and errata. Use consistent token art and sizing across compendia to avoid confusion in combat. Finally, create a fallback manual sheet for GMs to use if a system update changes automation behavior mid-event.

Fantasy Grounds: module packaging and compatibility Fantasy Grounds relies on packaged modules and the Fantasy Grounds ruleset to enforce mechanics. When you move Paizo materials into Fantasy Grounds, assemble modules that include the exact PDFs players will reference and the module entries for creatures, spells, and items. Verify that Fantasy Grounds interprets specific mechanics the same way as your reference PDFs: damage expressions, conditional modifiers, and triggered reactions are common points of mismatch. For organized play, distribute a short module notes file listing any local clarifications or house rulings that reconcile differences between the PDF wording and Fantasy Grounds implementation.

Statblocks, damage, and rule clarity: the mechanical checklist

A short mechanical checklist reduces argument time at the table. For each statblock and ability you migrate:

• Verify trait names and icons against the Paizo PDF
• Confirm damage dice and damage types match the original wording
• Test weakness, resistance, and immunity interactions in an isolated scene
• Run through triggered effects like reactions and focus points to ensure automation reflects intended timing

Record page references and errata lines so you can show the source if a player disputes a ruling. This reduces disputes and improves consistency across multiple GMs.

Batch preparation and quality assurance for events For conventions and multi-GM events, prepare in batches. Convert a single module fully and run a 60- to 90-minute playtest session in each target platform, with at least one GM unfamiliar with the conversion acting as a usability tester. That session will reveal interface friction, labeling problems, and encounter-timing issues you might miss in isolated checks. Maintain a shared event spreadsheet that lists platform, module name, compendium status, and a pass/fail column for automation checks so you can triage fixes quickly.

Player-facing materials and accessibility Make your migrations friendly for players who still prefer print or offline notes. Provide a clear inventory: which Paizo PDFs they should have, what is available in NEXUS, which compendia are active in Foundry, and what modules are loaded in Fantasy Grounds. Offer simple guidance for common fixes players can do themselves, like refreshing their compendium cache in Foundry or re-linking an updated PDF in Fantasy Grounds. Accessibility considerations include readable token sizes, consistent skill labeling, and color-contrast checks for anyone using high-contrast or large-font modes.

Patch management and post-migration governance After migration, appoint a point person for each platform: someone to monitor platform updates, import patches, and retest critical automation. Foundry and Fantasy Grounds both receive community updates that can change how rules are applied, and Demiplane NEXUS or Paizo may publish errata that affect encounters. Schedule a monthly or event-driven retest cycle that checks a representative sample of monsters, spells, and crucial abilities for drift between the PDF baseline and platform behavior.

Tools and workflows that speed the job Adopt a repeatable folder structure and naming convention that matches Paizo product codes or module names so you can find and patch content quickly. Use shared cloud storage for work-in-progress compendia exports, and tag items with a revision date and the source PDF page range. Build a small library of test scenes in Foundry and Fantasy Grounds that exercise common rules interactions so you can smoke-test a new import in ten to fifteen minutes.

Wrapping up: consistency matters more than perfect automation You will never achieve perfect parity across four distinct delivery methods, but you can ensure consistent player experience by treating Paizo PDFs as the authoritative source, validating every automated interaction in Foundry and Fantasy Grounds against that source, and managing licenses and distribution through NEXUS and the Paizo Store. With event-ready checklists, a short test battery for rules like damage and resistance, and one person assigned per platform, you will reduce in-session disputes and make your Pathfinder tables smoother, whether you run a weekly league or a weekend convention.

Final note: keep a lightweight log of changes tied to the Paizo page references so future GMs can trace why a mechanical tweak was made, and schedule a retest after any platform or errata update to protect the integrity of play.