Frequently asked questions

We currently support Magnolia and WordPress with native integrations. Connect your CMS, fetch definitions, and start migrating content immediately. We continuously expand platform coverage based on customer demand. Contact sales if your target CMS isn't currently listed.

Configuration typically requires 1–2 weeks for template mapping, component library setup, and workflow testing. Execution speed depends on page count and complexity – most teams migrate hundreds of pages in hours rather than weeks. Timeline includes discovery, snapshot capture, migration runs, validation cycles, and final sync to production. Iterative workflows let you start small, validate the approach, and scale when ready.

Yes. Trials include full access to migration features with no credit card required. Connect your CMS, fetch definitions, capture sample pages, and validate the complete workflow before purchasing.

The discovery agent crawls sitemaps and configured URLs, then capture workers fetch HTML, extract metadata, and generate visual screenshots. Each capture becomes a versioned snapshot stored in your workspace. Snapshots preserve source content at specific points in time. Capture new versions whenever source pages change, then re-run migrations against updated content.

Source snapshots, component libraries, and migration configurations live in your dedicated workspace. Your team controls access through user permissions and project boundaries. We don't access your content beyond providing the migration service. Enterprise customers can review data handling practices and storage locations during contract negotiation.

Not directly through automated discovery. For authenticated source sites, manually export HTML or use read-only service accounts that the capture workers can access. Some customers run internal proxies that handle authentication, then point Migration Accelerator at the proxy endpoints. Contact support for guidance on complex authentication scenarios.

During migration, the system extracts image URLs from source content and includes them in CMS-ready output. Enable DAM upload in platform configuration to automatically push assets to your target CMS during sync. Asset transformation (resizing, format conversion, optimization) depends on your target platform's capabilities and typically happens after Migration Accelerator completes its work.

Capture new snapshots and re-run migrations. The system maintains version history so you can compare changes, roll back if needed, or deploy different versions to staging versus production. Most teams establish snapshot cadences – capture daily during active migration periods, then weekly or on-demand after go-live.

Template mapping and component configuration require understanding of CSS selectors and your target CMS's structure. Teams typically include at least one person comfortable reading HTML and writing basic pattern expressions. Once configured, running migrations requires minimal technical knowledge. Content editors can capture snapshots, preview results, and sync to production using the web interface.

Yes. Use CSS selectors in template mapping to target specific content areas. Extract only the main article body, ignore navigation and footers, or pull specific components from complex pages. Template-level scope configuration ensures consistent extraction across pages matching the same URL pattern.

Component nesting, multi-column layouts, and conditional sections map to your target CMS's capabilities. Configure allowed components per area, preserve column structures where supported, and use validation rules to catch incompatible nesting patterns. Some complex structures require manual intervention – the system flags these during validation so teams can address them before sync.

The platform validates component schemas, required fields, nesting rules, and data types against your CMS's definitions before enabling sync. Validation errors include specific context – which page, component, and field failed. Coverage metrics show what percentage of source content successfully maps to target components. Use this data to improve extraction patterns and measure migration completeness.

Connect your Magnolia Author instance through platform configuration, then fetch template and component definitions directly from the `/mgnl-definitions/v1` API. The system imports structure metadata, field schemas, and nesting rules. Migrations validate against Magnolia schemas before sync. One-click sync from the Page Preview modal POSTs content to Author and refreshes live previews automatically.

Enterprise customers can configure multiple Author instances for staging, UAT, and production environments. Sync the same migration to different environments or maintain separate workflows per environment.

Standard authentication mechanisms (basic auth, bearer tokens, API keys) are supported through platform configuration. Complex authentication requiring OAuth flows or SSO integration may need professional services engagement. Contact support with your specific authentication requirements for feasibility assessment.

Credits represent migrated pages. Agency plans purchase credits in 500-page packs ($279). Credits never expire. Purchase what you need now and use remaining credits on future migrations or additional properties.

Trial: Full feature access with usage limits; no credit card required. Agency ($149/month): WordPress integration, unlimited projects, shared credits across team, standard support. Enterprise: Contact sales for custom pricing – includes dedicated account manager and priority support with guaranteed SLAs.

Yes. Upgrade from Trial to Agency or Enterprise anytime. Upgrade from Agency to Enterprise when you need Magnolia support or dedicated account management. Credits purchased at any tier remain available after upgrade.

Migration features continue working for existing projects – you can recapture snapshots, adjust mappings, and preview results. Purchase additional credit packs when ready to sync new content to your CMS. Agency customers can purchase additional 500-page packs anytime. Contact sales for Enterprise credit options.

Agency customers receive standard support through email and documentation. Response times typically within one business day for non-critical issues. Enterprise customers receive priority support with guaranteed SLA, dedicated account managers, and direct access to platform engineering for complex integration issues.

Enterprise plans include dedicated account managers who understand your CMS architecture and can troubleshoot complex configurations. Professional services engagements are available for hands-on migration execution, custom integration development, or training workshops. Contact sales to discuss professional services options.

Documentation covers platform features, migration workflows, and troubleshooting guidance. Enterprise customers can schedule training sessions for their migration teams.

Sign up at the Migration Accelerator website, create your first project, and configure platform connections. No credit card required. Full feature access with usage limits appropriate for testing and validation.

Gather target CMS credentials with API access, identify a subset of source pages for initial testing, and review your target platform's component structure. Teams move faster when they understand their target CMS's template and component architecture before configuring mappings.

Enterprise customers receive strategic planning support from account managers. Agency customers can access documentation, community resources, and email support for migration planning questions. For comprehensive planning assistance, inquire about professional services engagements that include discovery workshops, architecture review, and migration roadmap development.