How does the skill handle multiple platforms like Salesforce and HubSpot?

The skill groups all platform-specific instances (e.g., a Salesforce production org and a HubSpot portal) under a single parent folder for that specific organization, providing a 360-degree view of the client's infrastructure.

Can I test the folder reorganization before applying changes?

Yes, you can use the --dry-run flag with the migration command to preview all proposed changes and folder movements without actually writing to the disk.

Does this migration skill delete my original files?

No, the migration process is non-destructive. It copies files to the new client-centric structure and preserves the originals, ensuring no data loss during the reorganization.

Will my existing scripts and paths still work after migration?

The skill includes a path resolution utility and supports optional symlinks for backward compatibility, allowing your existing scripts to find files even if they have been moved to the new structure.

Client-Centric Folder Migration

Name: Client-Centric Folder Migration
Author: RevPalSFDC

byRevPalSFDC

•

Developer Tools

Migrates project data from system-centric folder structures to organization-centric architectures for improved multi-platform visibility.

The Client-Centric Migration skill automates the transition of project instance data from a legacy platform-first hierarchy to a modern, organization-first structure. By centralizing scattered platform data (such as Salesforce and HubSpot instances) under a unified organization boundary, it enables better cross-platform analysis, delivery, and planning. The tool includes robust safety features like dry-run previews, non-destructive file handling, and intelligent path resolution that maintains backward compatibility through symlinks and environment overrides, making it an essential utility for managing complex RevOps environments.

Key Features

01Dual-path resolution logic supporting legacy and new folder patterns

02Non-destructive migration process with optional backup and symlink support

03Automatic generation of machine-readable org and instance metadata

041 GitHub stars

05Automated migration from system-centric to org-centric directory structures

06Dry-run mode for previewing architectural changes without modifying files

Use Cases

01Consolidating scattered Salesforce and HubSpot instance data into a single client-focused directory

02Restructuring RevOps projects to improve visibility across multiple platforms for the same organization

03Automating the setup of standardized folder architectures for new client onboarding

Key Features

01Dual-path resolution logic supporting legacy and new folder patterns

02Non-destructive migration process with optional backup and symlink support

03Automatic generation of machine-readable org and instance metadata

041 GitHub stars

05Automated migration from system-centric to org-centric directory structures

06Dry-run mode for previewing architectural changes without modifying files

Use Cases

01Consolidating scattered Salesforce and HubSpot instance data into a single client-focused directory

02Restructuring RevOps projects to improve visibility across multiple platforms for the same organization

03Automating the setup of standardized folder architectures for new client onboarding