Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Preparing Data using Data Sync

  • You have configured Conga Data Sync to extract and transform data from your legacy system.
  • You have defined field mappings between legacy objects and Conga cart fields.
  • You have validated sample data sets and resolved critical data quality issues.
  • You have a bearer token with permissions to invoke migration endpoints.
You can migrate carts from your legacy system into Conga Advantage Platform and validated that the migrated data meets your quality and reconciliation requirements.
  1. Verify that Data Sync has completed successfully.
    • Ensure that the required objects (such as quotes, quote line items, and related accounts) are synchronized.
    • Confirm that field mappings for name, description, pricing, currency, effective date, and custom fields are correct.
    • Review run history to make sure no critical errors are present.
  2. Migrate a single cart using the Migrate Cart API.

    Use the legacy identifier and prepared cart data in the request.

    
    POST /api/cart/v1/carts/migrate
    Authorization: Bearer <token>
    Content-Type: application/json
    
    {
      "LegacyCartId": "LEGACY_CPQ_2024001",
      "MigrationConfig": {
        "PreservePricing": true,
        "RecalculatePricing": false,
        "PreserveApprovals": false,
        "UpdateStatus": "Migrated"
      },
      "CartData": {
        "Name": "Acme Corp - Enterprise Plan",
        "AccountId": "001xx000003DHP1",
        "Description": "Migrated from legacy CPQ system",
        "CurrencyCode": "USD",
        "EffectiveDate": "2024-01-01T00:00:00Z",
        "BillingPreference": "Annual",
        "Metadata": {
          "MigrationDate": "2025-03-05",
          "LegacySystem": "CPQ_v3.2",
          "MigrationBatch": "Batch001"
        },
        "LineItems": [
          {
            "ProductId": "Conga_Enterprise_License",
            "Quantity": 100,
            "UnitPrice": 500.00,
            "ExtendedPrice": 50000.00,
            "DiscountPercentage": 10,
            "DiscountAmount": 5000.00,
            "NetPrice": 45000.00
          }
        ],
        "TotalPrice": 51000.00
      }
    }
            

    Set PreservePricing to true when you need to retain legacy-calculated prices and discounts.

  3. Capture the migration response and monitor progress and verify that the response indicates migration has started.
    
    {
      "Status": "Migrating",
      "MigrationId": "mig_abc123",
      "CartId": "cartId_new123",
      "Message": "Cart migration initiated",
      "PollingUrl": "/api/cart/v1/carts/cartId_new123/status",
      "EstimatedDuration": "30 seconds",
      "NextPollIntervalMs": 1000
    }
            

    Use the provided PollingUrl to monitor migration status using the same polling pattern as cart activation.

  4. Perform batch migration when you migrate multiple carts. Use the batch endpoint to migrate a set of carts in a single operation.
    
    POST /api/cart/v1/carts/migrate/batch
    Authorization: Bearer <token>
    Content-Type: application/json
    
    {
      "BatchConfig": {
        "Name": "Legacy CPQ Batch 001",
        "Description": "First batch of 50 carts",
        "OnError": "Continue"  // or "Stop"
      },
      "Carts": [
        {
          "LegacyCartId": "LEGACY_001",
          "CartData": { ... }
        },
        {
          "LegacyCartId": "LEGACY_002",
          "CartData": { ... }
        }
      ]
    }
            

    Choose whether to stop or continue the batch when an individual cart fails using the OnError setting.

  5. Validate migrated carts after migration completes.
    • Retrieve migrated carts by their new CartId and compare key attributes to the legacy records.
    • Verify that line items, totals, and discounts match expected values.
    • Confirm that required custom fields and metadata are present and accurate.
  6. Reconcile and sign off on the migration.
    • Generate reports comparing counts and totals between legacy and migrated carts.
    • Spot-check a representative sample of migrated carts in detail.
    • Document any discrepancies and either correct them or record accepted deviations.
    • Obtain stakeholder approval before you decommission your legacy system.
You have migrated carts from your legacy system into Conga Advantage Platform and validated that the migrated data meets your quality and reconciliation requirements.