Migrate from Postman - Auk Documentation

Why Migrate to Auk?

If you’re using Postman and considering Auk, here are the key benefits:

Feature	Postman	Auk
Storage	Cloud-based	Local-first
Privacy	Data on Postman servers	Data on your device
Offline	Limited functionality	Full functionality
Cost	$12-49/user/month	Free
Collaboration	Cloud sync	Git-based
Speed	Network dependent	Instant
Data Control	Postman controls	You control

Migration Overview

The migration process involves:

Export collections from Postman
Export environments from Postman
Import into Auk workspace
Configure Git sync (optional)
Verify and test

Estimated Time: 15-30 minutes per workspace

Step 1: Export from Postman

Export Collections

Open Postman

Launch Postman desktop app or web version

Select Collection

In the sidebar, find the collection you want to export

Export Collection

Click the three dots (…) next to collection name
Select “Export”
Choose “Collection v2.1” (recommended)
Click “Export”
Save the JSON file

Repeat for All Collections

Repeat for each collection you want to migrate

Export all collections at once using Postman’s bulk export feature: Settings → Data → Export Data

Export Environments

Open Environments

Click “Environments” in Postman sidebar

Select Environment

Click on the environment you want to export

Export Environment

Click the three dots (…) next to environment name
Select “Export”
Save the JSON file

Repeat for All Environments

Export each environment separately

Postman environment exports include both initial and current values. Secret values may be masked.

Step 2: Prepare Auk Workspace

Create Workspace

Launch Auk
Create a new workspace or use existing one
Choose appropriate storage location
Optionally configure Git sync

Learn more about creating workspaces

Organize Structure

Plan your workspace structure:

Auk Workspace
├── Collections/
│   ├── API-v1/
│   ├── API-v2/
│   └── Internal-APIs/
└── Environments/
    ├── Development
    ├── Staging
    └── Production

Step 3: Import Collections

Import Single Collection

Open Import Dialog

Click “Collections” in Auk sidebar
Click “Import” button
Select “Postman” as import type

Select File

Click “Choose File”
Select the exported Postman collection JSON
Click “Open”

Configure Import

Import Options:

Destination: Choose target folder
Conflict Resolution:
- Replace existing
- Keep both
- Skip duplicates
Import Settings:
- Import scripts
- Import tests
- Import documentation

Review and Import

Review the collection structure preview
Click “Import”
Wait for import to complete

Verify Import

Open the imported collection
Check requests are present
Verify request details (URL, headers, body)
Test a few requests

Import Multiple Collections

For bulk import:

Click “Import” → “Postman”
Select multiple JSON files
Or drag and drop multiple files
Configure import options
Click “Import All”

Use Postman’s bulk export feature to get all collections in one file, then import that single file into Auk.

Step 4: Import Environments

Import Environment

Open Import Dialog

Click “Environments” in Auk sidebar
Click “Import” button
Select “Postman” as import type

Select File

Choose the exported Postman environment JSON file

Configure Import

Import Options:

Variable Mapping:
- Regular variables → Regular variables
- Secret variables → Secret variables
Value Selection:
- Use initial values
- Use current values
- Import both

Import

Click “Import” to complete

Set Secret Values

Open the imported environment
Find secret variables (marked with ***)
Enter the actual secret values
Save environment

Secret variable values are not exported by Postman for security. You’ll need to re-enter them in Auk.

Step 5: Verify Migration

Check Collections

Verify Structure:

All collections imported
Folder hierarchy preserved
Request names correct
Request order maintained

Verify Requests: Verify Scripts:

Pre-request scripts imported
Test scripts imported
Scripts syntax correct

Check Environments

Verify Variables:

All variables imported
Variable names correct
Initial values correct
Secret variables identified

Test Variables:

Variables resolve in requests
Environment switching works
Variable precedence correct

Test Requests

Send test requests to verify:

Select appropriate environment
Send a few representative requests
Verify responses are as expected
Check authentication works
Test variable substitution

Step 6: Configure Git Sync (Optional)

If you want team collaboration:

Create Git repository
Configure Git sync in workspace settings
Initial push of all collections
Share repository with team

Learn more about Git sync

Feature Mapping

Postman Features → Auk Equivalents

Postman Feature	Auk Equivalent	Notes
Collections	Collections	Direct mapping
Environments	Environments	Direct mapping
Workspaces	Workspaces	Local instead of cloud
Team Sync	Git Sync	Git-based collaboration
Variables	Variables	Same syntax `{{var}}` → `<<var>>`
Pre-request Scripts	Pre-request Scripts	Same functionality
Tests	Test Scripts	Same functionality
Collection Runner	Collection Runner	Same functionality
Mock Servers	Not available	Use local mock server
Monitors	Not available	Use external monitoring
API Documentation	Export to Markdown	Generate documentation
Version Control	Git	Built-in Git integration

Variable Syntax Change

Postman uses {{variable}}, Auk uses <<variable>>: Postman:

{{baseUrl}}/{{apiVersion}}/users

Auk:

<<baseUrl>>/<<apiVersion>>/users

Auk automatically converts {{variable}} to <<variable>> during import.

Script API Differences

Most Postman scripts work in Auk with minimal changes: Postman:

pm.environment.set("token", "value");
pm.test("Status is 200", () => {
  pm.response.to.have.status(200);
});

Auk:

pw.env.set("token", "value");
pw.test("Status is 200", () => {
  pw.expect(pw.response.status).toBe(200);
});

View complete script API reference

Common Issues and Solutions

Issue: Collections Not Importing

Problem: Import fails with error Solutions:

Verify JSON file is valid
Check file is Postman v2.1 format
Try exporting again from Postman
Check file size (very large collections may timeout)

Issue: Variables Not Working

Problem: Variables show as <<variable>> instead of values Solutions:

Check environment is active
Verify variable names match exactly
Check variable is defined in active environment
Remember: {{var}} → <<var>>

Issue: Scripts Not Working

Problem: Pre-request or test scripts fail Solutions:

Check script syntax
Update pm. to pw.
Check API differences
Review error messages in console

Issue: Authentication Not Working

Problem: Requests fail with auth errors Solutions:

Check auth type is supported
Verify credentials are correct
Check auth is configured at collection level
Test with simple request first

Issue: Missing Secret Values

Problem: Secret variables are empty Solutions:

Secret values are not exported by Postman
Manually enter secret values in Auk
Document secrets in README
Use password manager for team secrets

Migration Checklist

Use this checklist to ensure complete migration:

Pre-Migration

List all Postman workspaces to migrate
Identify all collections
Identify all environments
Document secret variables
Plan Auk workspace structure
Create backup of Postman data

Export Phase

Import Phase

Verification Phase

Post-Migration

Team Migration Strategy

Phased Approach

Phase 1: Pilot (Week 1)

Migrate one small project
Test with 1-2 team members
Identify issues
Refine process

Phase 2: Expansion (Week 2-3)

Migrate more projects
Onboard more team members
Setup Git repositories
Document workflows

Phase 3: Full Migration (Week 4+)

Migrate all projects
All team members on Auk
Decommission Postman
Monitor and support

Team Communication

Before Migration:

Announce migration plan
Explain benefits
Provide training
Set timeline

During Migration:

Daily standups
Slack/Teams channel for questions
Document issues and solutions
Celebrate milestones

After Migration:

Gather feedback
Address concerns
Continuous improvement
Share success stories

Cost Savings Calculator

Calculate your savings by switching from Postman to Auk: Postman Costs:

Team Size: 10 users
Plan: Professional ($29/user/month)
Annual Cost: 10 × $29 × 12 = $3,480/year

Auk Costs:

Team Size: 10 users
Plan: Free (local-first)
Annual Cost: $0/year

Optional Git Hosting:
- GitHub Team: $4/user/month = $480/year
- GitLab Free: $0/year
- Self-hosted: One-time setup cost

Total Annual Cost: $0-480/year

Savings: $3,000-3,480/year

Next Steps

Setup Git Sync

Configure Git for team collaboration

Best Practices

Learn local-first workflow

Script Migration

Update scripts for Auk

Team Collaboration

Git collaboration guide

Support

Need help with migration?

Documentation: auk.mamahuhu.dev
GitHub Issues: github.com/mamahuhu-io/auk/issues
Community: Join our discussions

We’re here to help make your migration smooth and successful!

Offline Usage From Insomnia

​Why Migrate to Auk?

​Migration Overview

​Step 1: Export from Postman

​Export Collections

​Export Environments

​Step 2: Prepare Auk Workspace

​Create Workspace

​Organize Structure

​Step 3: Import Collections

​Import Single Collection

​Import Multiple Collections

​Step 4: Import Environments

​Import Environment

​Step 5: Verify Migration

​Check Collections

​Check Environments

​Test Requests

​Step 6: Configure Git Sync (Optional)

​Feature Mapping

​Postman Features → Auk Equivalents

​Variable Syntax Change

​Script API Differences

​Common Issues and Solutions

​Issue: Collections Not Importing

​Issue: Variables Not Working

​Issue: Scripts Not Working

​Issue: Authentication Not Working

​Issue: Missing Secret Values

​Migration Checklist

​Pre-Migration

​Export Phase

​Import Phase

​Verification Phase

​Post-Migration

​Team Migration Strategy

​Phased Approach

​Team Communication

​Cost Savings Calculator

​Next Steps

Setup Git Sync

Best Practices

Script Migration

Team Collaboration

​Support

Why Migrate to Auk?

Migration Overview

Step 1: Export from Postman

Export Collections

Export Environments

Step 2: Prepare Auk Workspace

Create Workspace

Organize Structure

Step 3: Import Collections

Import Single Collection

Import Multiple Collections

Step 4: Import Environments

Import Environment

Step 5: Verify Migration

Check Collections

Check Environments

Test Requests

Step 6: Configure Git Sync (Optional)

Feature Mapping

Postman Features → Auk Equivalents

Variable Syntax Change

Script API Differences

Common Issues and Solutions

Issue: Collections Not Importing

Issue: Variables Not Working

Issue: Scripts Not Working

Issue: Authentication Not Working

Issue: Missing Secret Values

Migration Checklist

Pre-Migration

Export Phase

Import Phase

Verification Phase

Post-Migration

Team Migration Strategy

Phased Approach

Team Communication

Cost Savings Calculator

Next Steps

Support