Migrating from ServeManager — Proxiant Guides

1 What migrates automatically

Here is exactly what the Proxiant migration tool imports from ServeManager via their API, and what requires manual steps:

✅

Clients

Company name, contacts, email addresses, billing address

✅

Courts

Court name, address, county assignment

✅

Active and recent jobs

Job status, assigned server reference, due dates, full job history and attempt logs

✅

Affidavit templates

Converted to TipTap format; ServeManager variables remapped to Proxiant equivalents (see Section 4)

✅

Job number sequence

Set your Proxiant start number to continue directly from your last ServeManager job number

⚠️

Attempt photos

API limitation — download photos from ServeManager first, then re-upload manually to the relevant jobs in Proxiant

⚠️

Historical invoices

Import as read-only records for reference; active billing moves to Proxiant going forward

❌

Server accounts

Servers create free Proxiant accounts independently — you invite them by email after migration

2 Before you start

Complete these steps in ServeManager before initiating the migration:

Generate a ServeManager API key — go to Settings → API in ServeManager, create a new API key, and copy it. You'll paste it into Proxiant during migration.
Note your current job number — find the most recent job number in ServeManager. You'll set Proxiant to continue numbering from where ServeManager left off, so there's no overlap or gap in your records.
Download attempt photos for active jobs — optional, but recommended if you need photos for any jobs that are still in progress at migration time. ServeManager's API does not expose photos.
Invite your team to Proxiant before migrating — when the migration completes, all imported jobs become immediately visible to logged-in team members. Having your team in Proxiant before migration means there's no downtime.

⚠ Important: Don't cancel ServeManager yet. Keep it running in parallel throughout the transition period until all in-flight jobs are closed. See Section 5 for the recommended parallel approach.

3 Step-by-step migration

Settings › Migrations › Import from ServeManager

1

Go to Settings → Migrations in Proxiant

Found in your main Settings panel under the Data section.

2

Select "Import from ServeManager"

Choose ServeManager from the list of supported import sources.

3

Enter your ServeManager API key

Paste the API key you generated in ServeManager. Proxiant will validate the key before proceeding.

4

Preview what will import

Proxiant queries your ServeManager account and shows you a count of clients, courts, jobs, and templates ready to import. Review these numbers before confirming.

5

Confirm import

Click "Start Import." The import runs in the background — typically 2–10 minutes depending on your data volume. You'll receive a notification when complete.

6

Review imported data

Check your client list, court list, and job statuses. Spot-check a handful of imported jobs against their ServeManager originals to confirm accuracy.

7

Set job number format to continue your sequence

Go to Settings → Job Numbering, set the starting number to continue from your last ServeManager job number.

8

Configure rates

Billing rates are not imported from ServeManager — set them fresh in Proxiant. See the Billing Setup guide for details.

9

Invite servers to create free accounts and download the app

Go to Settings → Team → Servers and send invites. Servers create their own free Proxiant accounts and install the mobile app. Jobs assigned to them become visible immediately.

10

Go live

Use Proxiant for all new jobs from this point. Finish any remaining ServeManager jobs in ServeManager during the parallel transition period.

4 Template variable remapping

ServeManager templates use a different variable syntax than Proxiant. The migration tool automatically remaps common variables — here is the mapping reference if you need to manually verify or fix any templates:

ServeManager variable	Proxiant equivalent
`%server_name%`	`{{server.name}}`
`%server_license%`	`{{server.license}}`
`%company_name%`	`{{firm.name}}`
`%defendant%`	`{{recipient.name}}`
`%defendant_description%`	`{{recipient.description}}`
`%service_address%`	`{{service_address}}`
`%attempt_count%`	`{{attempt.count}}`
`%attempt1_date%`	`{{attempt.1.date}}`
`%attempt1_time%`	`{{attempt.1.time}}`
`%attempt1_result%`	`{{attempt.1.outcome}}`
`%attempt1_notes%`	`{{attempt.1.narrative}}`
`%served_date%`	`{{served.date}}`
`%served_time%`	`{{served.time}}`
`%court_name%`	`{{court.name}}`
`%case_number%`	`{{case.number}}`
`%plaintiff%`	`{{party_1_name}}`
`%job_number%`	`{{job.number}}`
`%today%`	`{{today.date}}`

ℹ Note: Any ServeManager variable not in the above mapping will appear as unresolved (shown in red) in the Proxiant template editor after migration. Open each imported template and check for red variables before publishing.

5 Running parallel during the transition

The cleanest migration strategy is to run ServeManager and Proxiant in parallel for a short transition window rather than doing a hard cutover. Here is the recommended approach:

For jobs already in progress in ServeManager

Finish them in ServeManager. Even though those jobs are now visible in Proxiant (imported), continue logging attempts and generating affidavits from ServeManager until those specific jobs are closed. This avoids mid-job confusion and keeps your historical records clean.

For all new jobs from migration day forward

Enter them in Proxiant only. Do not create new jobs in ServeManager after you go live on Proxiant. Your team should understand the cutover date clearly.

How long to run parallel

Most firms need 1–3 weeks of parallel running, depending on their average job cycle time. Once all pre-migration jobs are closed in ServeManager, you can stop using it and cancel your subscription.

⚠ Important: Don't cancel ServeManager until all in-flight jobs are closed there — run parallel for the full transition period. Cancelling early risks losing access to job history you may need for court filings.

6 After migration checklist

Use this checklist to confirm your Proxiant setup is complete before relying on it for production work:

Client list reviewed and accurate — spot-check names, emails, and billing addresses

Court list reviewed — verify court names and county assignments

At least one affidavit template configured and test-generated per job type

Rate tables configured (billing rates are not imported — must be set fresh)

Team (admins and staff) invited and logged in

Servers invited to create free accounts and download the mobile app

Job numbering continues from ServeManager sequence — no gaps or duplicates

Client portal configured (optional — see the Client Portal guide)

Team briefed on cutover date — new jobs enter Proxiant only from this date

ServeManager kept active until all in-flight jobs from before migration date are closed

✓ Questions during migration? Contact us — we'll help. Most migrations take under an hour with support. Reach us via the chat widget in your dashboard or at support@proxiant.co.