Skip to main content
Project import lets you bring an existing application from another hosting platform into Pxxl without starting from scratch. When you supply a provider API key, Pxxl reads the project’s repository connection, detected framework, build commands, install commands, start commands, and available environment variables — then pre-fills the Pxxl project creation form with that data. The result is a normal Pxxl project that you manage exactly like any other project after creation. Open Dashboard > Projects > Add New > Import Project to begin. You can also open Dashboard > Deploy Project and choose the import option when it is available.

​
Import Flow

1

Provider access

Choose your current hosting provider — Vercel, Netlify, Render, or Railway — paste your provider API key, decide whether to save it encrypted for future imports, then click Fetch Projects. Pxxl calls the provider API and loads your available projects.
2

Select project

Search the fetched project list and select the application or service you want to move to Pxxl. The project card may show the provider name, repository URL, detected framework, build command, install command, start command, and a summary of available environment variables.If a project is missing from the list, verify that the provider token belongs to the correct account or team, confirm that the GitHub owner or organization is connected to your Pxxl workspace, then fetch again.
3

Confirm create

Review every field that Pxxl pre-filled from the provider before creating the project. When everything is correct, click Create Pxxl project.
FieldWhat to verify
Project nameBecomes the Pxxl project name and suggested subdomain. Use lowercase letters, numbers, and hyphens.
PortThe port your application listens on inside the runtime. Node.js apps commonly use 3000, but apps should read PORT when possible.
Domain optionChoose whether Pxxl should create a Pxxl subdomain immediately. Custom domains can be added later from the project or domain pages.
GitHub branchThe branch Pxxl deploys first.
CommandsReview install, build, and start commands. Override provider values if the application needs different commands on Pxxl.
Environment variablesImport available provider variables and add any missing or masked values manually.

​
Provider Key Guides

Netlify tokens are useful for importing site metadata, repository connections, build settings, and environment variables the Netlify API exposes.
  1. Open Netlify > User settings > Applications.
  2. Scroll to Personal access tokens.
  3. Click New access token.
  4. Give the token a clear label, such as Pxxl import.
  5. Choose a short expiration when possible.
  6. Create the token and copy it once — Netlify will not show it again.
  7. Return to Pxxl, paste the token into the provider key field, keep Save encrypted key enabled only if you plan future Netlify imports, then click Fetch Projects.

​
Environment Variables During Import

Providers do not always expose secret values through their APIs after a variable has been created. When a provider returns only variable names or masked values, you must add the real values manually — either in the import form before creating the project, or afterwards under Project > Environment Variables. Recommended pattern:
  1. Import non-secret metadata automatically from the provider.
  2. Add required secrets and masked values manually in the confirm-create form.
  3. Click Create Pxxl project and monitor the first build.
  4. Open Project > Live Logs if the application does not start — a missing variable is the most common cause.
  5. Rotate or revoke the provider token once the project is running and migration is confirmed complete.

​
After Import

Once the Pxxl project exists, manage it exactly as you would any project created directly from GitHub.
Next stepWhere to go
Check build statusProject > Deployments
Watch runtime outputProject > Live Logs
Add or correct secretsProject > Environment Variables
Attach a custom domainProject > Domains or Manage Domains
Tune resourcesProject > Infra & Scaling
Change repository or protection settingsProject > Settings
Security checklist — follow these steps for every import:
  1. Use provider tokens with the shortest practical expiration.
  2. Save the key encrypted in Pxxl only when you expect future imports from that provider.
  3. Never paste provider tokens into screenshots, chat messages, commits, or support tickets.
  4. Revoke one-time migration tokens from the provider dashboard after the project imports successfully.
  5. Rotate any imported application secrets — database passwords, third-party API keys — if they may have been exposed during the migration process.