Migrate from PromoXcrm to HighLevel

PromoXcrm Leads map to GoHighLevel Contacts. PromoXcrm's industry-specific pipeline stages (Quote Sent, Artwork Approved, Order Confirmed) are text fields that we map to GoHighLevel pipeline stage values configured before migration. Any PromoXcrm custom fields on the Lead record require corresponding GoHighLevel custom field creation; we document each field name, type, and options in the pre-migration schema sheet.

PromoXcrm Client records (the distributor's end customers) map to GoHighLevel Contacts with an associated Company record when a company name is present. Standard fields — name, email, phone, address — migrate directly. Any promo-specific custom properties on the Client record (client tier, preferred supplier, referral source) require GoHighLevel custom field creation before import.

PromoXcrm pipelines with promo lifecycle stages map to GoHighLevel Pipelines. We pre-create the GoHighLevel pipeline and configure stage names matching PromoXcrm's workflow (Quote Sent, Artwork Approved, Order Confirmed, Fulfilled). Stage probability values migrate as GoHighLevel stage probabilities. Pipeline assignment per deal is preserved in a custom field if the destination GoHighLevel account uses multiple pipelines.

PromoXcrm Projects (individual promo orders or campaigns tied to a client) map to GoHighLevel Opportunities. We preserve the project name as the Opportunity name, the project status as a custom Opportunity status field, and link the Opportunity to the Contact and Company records created from the corresponding PromoXcrm Client. Projects without a deal value map with zero amount and a custom project_type__c field set to Project.

PromoXcrm Tasks migrate to GoHighLevel Tasks with assignee, due date, status, and description preserved. PromoXcrm's automated task-creation rules tied to pipeline stages do not transfer; we document each active automation as a written trigger-action pair with a recommended GoHighLevel Workflow equivalent for the customer's admin to rebuild.

PromoXcrm Presentations are file assets stored within the CRM. We export available file references and metadata, then re-upload files to GoHighLevel's native file storage linked to the corresponding Contact or Opportunity record. Actual file hosting transfer depends on PromoXcrm's export capabilities; if PromoXcrm does not expose files via API or export, we document the file URLs and filenames for manual re-upload.

Commission Records are a PromoXcrm-specific feature for tracking rep or distributor earnings on promo orders. GoHighLevel has no standard commission object; we create a GoHighLevel Custom Object (commission_records) with fields for rep name, order reference, commission amount, and payout status. The custom object schema must be created in GoHighLevel before any commission data can be imported via CSV. We coordinate the schema design with the customer during the schema design step.

PromoXcrm's custom objects accessible via its web-service API migrate to GoHighLevel Custom Objects. We probe PromoXcrm's API during discovery to enumerate the custom object schema, then pre-create the corresponding GoHighLevel Custom Object definitions including fields, types, and lookup relationships before any data import. Each custom object requires CSV import into GoHighLevel after the schema is validated in a test run.

PromoXcrm integrations with Xero, Stripe, and Mailchimp are native connection configurations, not data records. These settings do not export. We document which integrations were active in PromoXcrm, the credentials or OAuth connections required, and provide a reconnection guide for configuring equivalent integrations in GoHighLevel (GoHighLevel has native Stripe and Xero integrations plus a broader Zapier and webhook ecosystem).

PromoXcrm's reporting system generates analytics from live data. Saved report configurations and dashboard layouts are not exportable as standalone objects. We export the underlying data — Contacts, Deals, Tasks, Custom Objects — so that equivalent reports can be built in GoHighLevel using GoHighLevel's native reporting tools. We do not rebuild reports as part of the migration scope.