In This Section
- Concepts
- Data
- Build
- The App Composer
- The Page Index
- Context
- Pages
- Models
- Components
- Best Practices
- Debugging Skuid in the Console
- Logic
- Style
- Deploy
- Extend
- Reference
- The Property Library
- API Reference
- skuid.debug
- skuid.runtime
- skuid.$
- skuid.actions
- skuid.ajax
- skuid.builder.core
- skuid.builder.core.coreProps
- skuid.calendar
- skuid.collaboration
- skuid.component
- skuid.componentType
- skuid.events
- skuid.formula
- skuid.hotkeys
- skuid.label
- skuid.lightning
- skuid.load
- skuid.model
- skuid.model.Model
- skuid.mustache
- skuid.page
- skuid.sfdc
- skuid.snippet
- skuid.time
- skuid.utils
- skuid.version
- Component-Specific APIs
- Skuid Model Metadata Object
- Skuid Model Child Relationship Metadata Object
- Skuid Model Condition Metadata Object
- Skuid Model Field Metadata Object
- Skuid Model Record Type Metadata Object
- Page XML API
- skuid-sfdx
- skuid CLI
- Skuid Metadata Object Reference
- Skuid Glossary
- Formula and Function Reference
- Open Source Software Attributions
- Site Administration
- Tutorials
- Legal terms and conditions
- Skuid for Salesforce Evaluation Guide
What happens if I need to migrate to Lightning after building with Skuid in Classic?¶
Skuid is compatible with VisualForce and Lightning environments.
A migration from Classic to Lightning will not necessarily require a rebuilding of Skuid pages.
There may be some adjustments that must be made to the Skuid pages after the migration. For example, if URL navigation on the Skuid pages included absolute links or relative links with Classic-specific references, then any Skuid page with URL navigation actions will need to be modified after the migration.
When migrating from Classic to Lightning, add Skuid pages to Lightning pages via the Lightning App Builder.