Integrations, CRM and data migration

Systems exchange data on their own, with no copying by hand.

$1,780 to link two systems · $2,700 for a CRM rollout.

Get a quote

Who copies enquiries from email into your CRM?

Usually the office administrator, between calls. The same company is entered three different ways in three systems. Invoices go out on data already out of date. The monthly report is pulled together by hand in a spreadsheet, and it does not always add up. A manager who left took half your contacts with them.

Data moves on its own

The same enquiry is no longer keyed in by hand in three places. First on paper: which fields, in which direction, and which side wins when the data disagrees. You sign that off before the first line of code — a change at this stage costs an email, not a week.

If the other system does not answer, the record is not lost: it waits in the queue and goes again by itself. Everything that failed shows up in the error report the same day, not a quarter later, when the numbers stop adding up.

History goes onto a copy first and is checked against row counts and totals — only then do we switch over. You can roll everything back until the end of the period we agreed.

  • included: A review of your systems and a written exchange spec before work starts
  • included: A field map: what goes where, and in which direction
  • included: Which side wins when the data disagrees
  • included: Automatic retries and an error report by email
  • included: Migration onto a copy first, checked against row counts
  • included: Switch-over on the agreed date, with a way back
  • included: A written guide and handover of access to your team
  • included: We watch the exchange for the first thirty days
  • paid to the vendor: Third-party licences and plans — at the vendor's invoice

Your price

Two systems joined up

$1,780 per link

One two-way exchange

What the tier includes

  • included: A field map and which side wins
  • included: Two-way exchange, every send visible
  • included: Retries when the other side fails
  • included: Monitoring for the first thirty days

CRM rollout

$2,700 per rollout

Pipeline, fields, permissions and data import

What the tier includes

  • included: A pipeline and stages built round your sale
  • included: Fields, permissions and staff roles
  • included: Import of your contacts and companies
  • included: Training, with the session recorded
  • paid to the vendor: The CRM licence — at the vendor's invoice

Data migration

$1,860 per source

Up to a hundred thousand rows, then in steps

What the tier includes

  • included: Up to a hundred thousand rows from one source
  • included: Migration onto a copy first, then a check
  • included: Switch-over, with a way back
  • not included: Over a hundred thousand rows — $3,030 per source
  • not included: Over five hundred thousand — $3,930 per source

Extras

  • not included: A CRM rollout from scratch$2,700 per rollout
  • not included: Data moved over from another systemfrom $1,860 per source
  • not included: An app built around your processfrom $14,400 per project
  • not included: A website or online shopfrom $1,430 per project
  • not included: Site care and hostingfrom $99 a month
  • not included: Analytics set up: see where customers come from$1,800 per set-up
  • not included: Moving off QuickBooks Desktop$1,799 per file
  • not included: Changes after the link goes live$90 an hour

Questions

Our software is old and has no exchange interface. What then?

The exchange is still possible: files on a schedule, straight from the database, or through a middleman that reads reports out of the mailbox. We pick the method at the review, and say there what each one will stand and where it will break.

What happens to the data if the other system does not answer?

Nothing is lost. The record stays in the queue, goes again, and lands in the error report that reaches you by email. An exchange that keeps quiet about losses is found a quarter later, and untangling it costs more than building it again.

How long does the link last after handover?

As long as both systems last. Updates on the other side break the exchange once every year or eighteen months; the first thirty days of monitoring are in the price, after that it is either a development subscription or one-off work by the hour.

Will the data have to go outside?

No. The data moves between your systems, not outside them. Everyone who works with it has their own login and only the rights they need. What goes where is written in the field map before work starts, and after handover the access is put in your team's name.

Where to send the quote

Name the two systems you need linked — we will send the price and the timeline by email.

When to start
Which systems we are linking